Quality Testing

Quality is delighting customers

Some aspects related to Endurance testing:

  • It basically comes under non-functional testing.

  • It is intended to check the memory leaks.

  • The objective is to find out how the system acts under continuous use. That is, to guarantee that the throughput or/and reaction times after some long stretch of continuous activity are as good or superior than at the start of the test.

  • Endurance testing consists of testing a system with a critical load reached out over a noteworthy time-frame, to find how the system functions under sustained load. For instance, in software testing, a system might continue to function on exactly as expected when tested for 1 hour, yet, when the same system is tested for 3 hours, issues, e.g. memory leaks lead the system to break down or act in a random manner.

Time frame necessary for Endurance Testing:

Endurance testing requires a lot of time since the basic intention is to verify performance of the system over delayed use. The time span for a test is finalized on the premise of variables like client involvement, actual production, utilization of system and so on. One test for such type of testing may take well more than 12 hours to be finished. A few organizations even carry out this type of testing for a period of one year.

Endurance Testing Lifecycle:

  • Analysis of requirements:

In this stage, the prerequisites are analyzed and understood. This phase is in charge of recognizing which type of testing tramadol should be performed. E.g. if it’s a brand new software then, this testing will probably be pin scope. In any case, in the event that it is only an addendum to an established software, then, endurance testing can be ruled out.

  • Test plan:

Amid this phase, resources, time frames and cost estimation is carried out for the test cases. The extent of automation and manual testing too is chosen amid this stage. Endurance testing is done utilizing automation tools like LoadStorm. As examined before, this testing is a tedious procedure. The schedule is chosen in light of the variables like budget, client requirement and so on.

  • Test case development:

Test Cases are designed amid this phase. The workload and duration for testing is chosen amid this stage. An endurance test case may keep running from 12 to 72 hours in view of the requirements. In any case, once in a while, client can give clear specifications and duration can be decreased up to 3 or 4 hours, according to client need.

  • Testing environment:

Test Environment is created amid this stage. The environment for such type of testing ought to be disengaged from other test conditions. It ought to be like genuine production environment with the goal that outcomes produced are exact and consistent. Likewise, original environment ought to never be utilized for testing as a system crash amid testing may affect the environment and cause loss of data.

  • Test case execution:

Problems like memory leaks, moderate reaction time, database connection issues are distinguished and resolved.

  • Closure:

In view of exit criteria set amid test planning test cycle ought to be shut. Exit criteria could be defined based on the timeline or the defects found.

 

Views: 15

Reply to This

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2017   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service