Sep 14, 2018
Description of the Service.
For every performance software service performed by the Software testing service provider, two documents are available to the customer according to each project. The Test Plan and the Collection Plan. The Test Plan consists of presenting to the client all the description and stages of the test. As its purpose, the scope, timeline, test grid, and the scenarios (step by step) to be tested (Test Scenarios).
Another important point of the Test Plan is to describe how the accesses will be distributed. Or, for each number of simultaneous accesses, how many will simulate the A functionality, the B functionality, and so on. The Collection Plan consists of documenting the procedures to generate performance collections during the execution of the activities. That is, which monitors will be activated, in which moments will be generated dumps of the application under test, how will be carried out an application profiler or make collections in the database.
All the collection is described step by step and documented so that in the execution of the test, it is possible to extract the necessary information of the performance of the environment and software tested
The Load Test:
One of the types of Performance Test is the load test. It is usually performed to identify the behavior of the system under an expected specific load. What can be an expected number of concurrent users, a number of operations per hour, or a certain number of transactions in the system being tested? This type of test is ideal for checking whether the application, web server or database under test, maintains good behavior during its usual workload.
The Stress Testing:
This type of Test is performed to verify the behavior of the environment and software during an extreme load. Also to determine if the system under test will perform sufficient operations above the expected maximum.
Long-term test or Resistance test:
Soak testing or resistance testing is to determine if the system under test can withstand continuous loading over long periods of time. Determines whether the software under test will behave properly in memory usage over a long period of use, for example. Another important point of this type of test is to verify that there is no deterioration in performance after 4 or 8 hours of continuous use. In order to guarantee that it meets the normal periods of production in which the system will be used.
Quick Rise Test:
This type of simulation test is performed a fast and great rise of concurrent users in a short period of time. The goal is to determine whether the system under test will fail or succeed in dealing with a sudden change in user load.
Instead of testing performance in a loading view, configuration tests are designed to determine behavior in configuration changes for an environmental component. For example, what will performance be like when modifying load balancing, removing or adding new servers, using a contingency link, or any other modification that occurs in the test environment.
- (no comments)