Deriving the Test Cases for Performance Tests.

The primary input for performance test cases are the Supplementary Specifications, which contain the non-functional requirements. Use the following guidelines while deriving the test cases for performance test:

1. Ensure there is atleast one test case identified for each statement in the supplementary specification, which states performance criteria. Performance criteria are usually expressed as time per transaction, number of transactions / users or percentiles.
2. Ensures there is atleast one test case identified for each critical use case. Critical use cases are those identified in the above statements and / or in the workload analysis document that must be evaluated using performance measures.

As with test cases for functional tests, there will typically be more than one test case per use case / requirement. It is more common that there will be one test case that is below the performance threshold value another at the threshold value, and a third test case above the threshold value.

In addition to the above performance criteria, ensure that you identify the specific conditions that affect response times, including:

3. Size of the database – how many records exists?
4. Workload – number and type of simultaneous end-users, number and type of simultaneous transactions being performed.
5. Environment characteristics (Hardware, Netware, Software configuration).

Capture test cases for performance test in matrices similar to those used for functional test.

Below are some examples for the different types of Performance Tests:

For Load Test:

TC ID #------Workload-----Condition-------------------------------------Expected Result
TC_LD_01----10 Users-----Can be able to access the application---Successfully able to access the application.
TC_LD_02----500 Users----Can be able to access the application---Successfully able to access the application.
TC_LD_03----1000 Users---Can be able to access the application---Successfully able to access the application.

For Stress Test:

TC ID #------Workload-----Condition-----------------------------------------------Expected Result
TC_ST_01----10 Users-----11 th User logged in------------------------------------Request will be queued
TC_ST_02----500 Users----Server is down------------------------------------------Transaction is queued or times out
TC_ST_03----1000 Users---Communication terminates during transaction---Warning message will be displayed

Comments

I every time emailed this

I every time emailed this webpage post page to
all my associates, since if like to read it afterward my links will too.

I seldom leave comments, but

I seldom leave comments, but i did some searching and wound up here Deriving the Test Cases for Performance Tests.
| QA and Testing Tutorial. And I actually do have 2 questions for you
if it's allright. Is it only me or does it seem like
some of these comments come across like they are coming from brain dead visitors?
:-P And, if you are posting on other places, I'd like to follow everything new
you have to post. Would you make a list of every one of all your community sites like your twitter feed, Facebook page or linkedin profile?

Nice Post

An excellent tutorial and I must say that it is a perfect way to describe such thing.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.