Defining Your Scenario
Defining your scenario is one of the most important steps of the entire performance testing process. Without a defined test scenario, multiple problems are likely to arise as you begin or conclude your performance tests.
Follow the points listed below when creating your scenario:
- Put your test scenario into words and a
flowchart.
This allows you to create a clear picture of the requirements and the solution necessary to meet them.
- Ensure the script you're building is compliant with the scenario you've designed. Compare the scenario with the script and see if the requirements expected will meet the criteria set out in your scripts.
-
Perform a simple one user test. This will help you understand if the application functions as expected and if any changes have been made within the database. Run a sample multi-user test to confirm if the data files are functioning as expected and then re-confirm your results and determine if a real time scenario is replicable with the test.
- Determine whether the Thread Controllers support your use-case scenario. If not, you might have to make changes to the original script(s), or create a set of test plans. You should also check any and all plugins that you're using within your website framework. You may be using plugins developed by enthusiasts in the industry, so make sure that the controllers meet your expectations and application needs. Google plugins come with three wonderful controllers that can meet most requirements.
- Be aware of the business problems and risks you're
trying to mitigate through testing. Have a clear idea of
the scenario that you're planning to execute and then test against.
This will help you to create or configure other important pre-test
settings while designing the scenario and performance tests.
The most commonly used pre-test settings include:
- First time user and the revisiting user scenario
- Thinktime & Pacing time
- Cache behavior
- Browser emulation
- Bandwidth provision
-
Image: Default configuration
in JMeter Pro.