https://training-course-material.com/index.php?action=history&feed=atom&title=What_to_TestWhat to Test - Revision history2026-05-13T09:38:49ZRevision history for this page on the wikiMediaWiki 1.45.1https://training-course-material.com/index.php?title=What_to_Test&diff=23918&oldid=prevCesar Chew at 16:38, 24 November 20142014-11-24T16:38:59Z<p></p>
<p><b>New page</b></p><div>{{Cat|JMeter|30}}<br />
<br />
== Performance Testing Requirements ==<br />
* Non functional requirements come from the business strategy or contract with clients<br />
** e.g. If the strategy is to have few rich visitors test should focus on reliability rather than expect billions of visitors<br />
* Subset of functional testing (Use Cases, User Stories and their Scenarios)<br />
* Most frequent scenarios<br />
* Scenario which potentially impacts performance<br />
* Prioritized by business people (managers) not testers<br />
* Not everything should be tested<br />
* Setting goals and scope of test is crucial (otherwise it is never done) <br />
* Testing can be a continuous process<br />
<br />
== Performance Requirements ==<br />
* Specific Hardware (8 Athlon Processors, 512MB RAM, SSD, etc..)<br />
* Software Confiugration<br />
* Max no of records in the database (e.g. 100 000 000)<br />
** Can be express in business terms (number of clients, contacts, invoices, enquiries, etc...)<br />
* Max database size (e.g. 100 GB)<br />
* Maximum number of registered user (e.g. 4500)<br />
* Distribution of scenarios: scenarios 1 (20%), scenario 2 (30%), scenario 6 (70%)<br />
** Average Response Time (e.g. 1500ms)<br />
** Maximum page load time (e.g. 10 sec)<br />
** Minimum throughput (e.g. 2400 pages/minute)<br />
** Concurrency users (300 users working concurrently)<br />
<br />
== Performance Test results ==<br />
'''Client side''':<br />
* Response Time: distribution shape, min, max, average, standard deviation, median, skewness<br />
* Throughput (scenarios/min)<br />
* Error Level, error responses in details<br />
'''Servers side''':<br />
* Memory utilization<br />
* CPU utilization<br />
* Network throughput<br />
* IO waiting time<br />
* Storage free space<br />
<br />
== Performance Testing Process ==<br />
* How to identify your testing needs <br />
* Defining the steps of your test<br />
** Gathering requirements (use cases, user stories)<br />
** Scoping (choosing and prioritize scenarios)<br />
** Designing tests<br />
** Preparing data<br />
** Preparing environment<br />
** '''Recording tests'''<br />
** '''Perform the test'''<br />
** '''Analysis and reports'''<br />
** Conclusions and improvement</div>Cesar Chew