Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
14 Cards in this Set
- Front
- Back
|
Manual Performance Testing techniques include:
|
Stopwatch
Use people (representative of live) traffic in a controlled manner on a test environment |
|
|
Automated Performance Testing techniques include:
|
Data driven techniques
Load testing Stress testing Capacity Testing Reliability/Endurance Testing |
|
|
Confidence Building Tests techniques include:
|
Own data
Test system Live data Live system |
|
|
V-Model based testing techniques include:
|
Top down model of Performance Testing
Bottom up model of Performance Testing |
|
|
Other testing techniques:
|
Use Historical analysis of existing system
Operational profiles |
|
|
Business Specification
|
Contains a number of business functions which are units of work, or navigational steps, that application users perform to complete a business task.
|
|
|
Test Case
|
Provides the detailed information necessary to verify or validate a test item for a work product in a given operating condition.
|
|
|
Test Scenario
|
Executable test files that are used to automate the Performance Test.
|
|
|
Test Script
|
Executable test routines that are used to automate business functions.
|
|
|
Reliability (Endurance)
|
Test of a system over time; the goal is to achieve steady state of virtual users submitting requests to the system for several hours.
|
|
|
Response
|
Replicate real-life use of an application, performed in order to access how the application will work under actual conditions of use.
|
|
|
Stress
|
Designed to determine how heavy of a load the application can handle or how much headroom the infrastructure has available.
|
|
|
Load Testing
|
Refers to simulating the behavior of many users accessing and using the system at the same time, thus putting a load on the system. As the tests are executed, response time and other performance metrics are captured. These metrics can be used to determine if requirements are met, if the test case was successful, to benchmark the application and identify bottlenecks.
|
|
|
Test cases should include the following items:
|
Test Case Identifier
Description Inputs Execution Procedures Expected Results |
