Skip to main content

Important Set up before load Testing

By

Important Set up before load testing includes:

1.       A suitable time to load-test the application, for instance when no development work is taking place on the server (load testing may cause the server to crash) and/or no other users are accessing the server (else the testing results would not yield the correct measures)
2.       The performance metrics, accepted levels, or SLAs and goals
3.       Objectives of the test
4.       The Internet protocol(s) the application is(are) using (HTTPS, HTTP, FTP, etc.)
5.       If your application has a state, the method used to manage it (URL rewriting, cookies, etc.)
6.       The workload at normal time and at peak time
7.       Before load or performance testing application should be stable at least tested at once through the manual method
8.       Before load testing, do not record any page, which has 404 or server errors
9.       During load test don’t do real transaction or any money ready work.
10.   During load testing try to maintain  the real scenario as user experience
11.   Use meaningful test scenarios (use cases are helpful) to construct test plans with 'real-life' test cases.
12.   Make sure that the machine running Load testing tool has sufficient network bandwidth, so the network connection has little to no impact on the results.
13.   Let Load Test run for long time periods, hours or days, or for a large number of iterations. This may yield a smaller standard deviation, giving better average results. In addition, this practice may test system availability rate and may highlight any decay in server performance.
14.   Ensure that the application is stable and optimized for one user before testing it for concurrent users.
15.   Incorporate 'thinking time' or delays using Timers in your Load testing scenario Test Plan. 
 16  Keep a close watch on the four main things: processor, memory, disk, and network.
17.   Only run Load testing tool against servers that you are assigned to test, else you may be accused of causing DoS attacks.
Labels:

Comments

Post a Comment

Popular posts from this blog

Steps To Hunt the Bugs Successfully

By
The testers should catch the bugs in software that they’re testing. Testers should try to catch as several vital bugs as soon as possible. Catching the crucial bug earlier on Product-Life-Cycle can save the Projects from financial losses & mitigate the risks as compared for catching the same at a later stage in SDLC. Steps to hunt the bugs: Sometimes it’s useful to break the rules: The following test cases, which were predefined a tester can miss the bugs so it makes it impossible’s to provide the product i.e. 100 percent bug free. If you-follow pre-determined test cases you risks becoming blind to outside the bugs. A first secret is to check the functionality under the test. It’ll be an effective channel to discover the more bugs, because functionality is not generally covered by the test cases. Examine the patterns: You might have noticed that the bugs can be often met in the groups, one can call them-gregarious. The testing a new but the similar functionality...
Post a Comment
Read more

Cross browser testing Tools

By
Cross Browser testing It is a process to test the web apps across multiple browsers. It involves the checking compatibility of the app across multiple web browsers & ensures that your web app’s works correctly across different web browsers. Tools for Cross Browser Testing Browser shots: The browser shots might be most exhaustive cross browser-testing tool that exists. Browser Shots includes all of most popular-browsers, like Firefox, Chrome, & Safari, along with the tons of another browser’s that might sound unfamiliar, like Sea Monkey, Flock, & Iceape. You can adjust the resolution, color-settings, & even Flash and JavaScript settings. Cross Browser Testing: It allows users to test their websites with over the hundred resolution or browser and Operating System combinations. This also has support to mobile web-browsers, which is crucial because the web traffic is making shift from the primarily desktop computer users to primarily mobile ...
Post a Comment
Read more

Mobile Application Testing: Strategy for Development

By
There are a huge number of demands and lots of competitions in the mobile application industries. In that demands and competitions, the mobile application testing has become more important. The testing phase of the mobile application testing looks like evil between the creative process and excitement of new products in the market. According to the survey, “In US, on an average 2-3 hours per day people spends their time on smartphones and tablets. On that time, they spent 80% on mobile application and remaining 20% on web applications.” Few list of key factors for successful mobile application testing strategies are: Selection of Device for Testing : Before introducing the mobile application test activities, first select the devices for testing the application. Selection decision is very important because only devices can help to targets maximum numbers of the customers for accessing the application. There are two parts for device selection: §   Device Model ...
Post a Comment
Read more