Skip to content

Performance Testing :: Module 3 :: 5.1 Creating/Updating scripts :: Read

This article is a part of the Self-paced Learning Series for the Course: First-Hand Experience of WorkSoft SaaS.

Please refer to the link for more details on the Course.

Creating/Building the test script and commands for capturing metrics


When you build automation to test your functionality, there is no restriction as to how you build test scripts. As a best practice at eureQa, we recommend that you keep these as granular as possible. If you have followed this practice, you will congratulate yourself as the amount of re-work you need to do is minimal to none. If your test scripts are longer, take a pause here and break the scripts into smaller ones. Typically an action (that involves backend calls) followed by verification has to be part of one test script. For you to capture response times, action command should be one of the following commands
  • assertText
  • assertTitle
  • assertVisible
  • click
  • sendKeysTabOut
  • storeVisible
  • waitForText
  • waitForVisible
  • wsExecuteRequest
  • runEventTimingFunction
Lets start editing our existing scripts to verify/add above commands.

1. Verify commands for existing functional flows: in our existing business scenario, one of the test scripts is identified as usage steps and lets verify the same. The Test script is Launch URL. In launch URL Test Script, we are going to open & assertVisible to launch the home page and to wait until desired element is loaded.

2. Create new test scripts as usage steps: Use the QaSCRIBE<attach link for creating test script using QaSCRIBE> to record the new script. While recording, make sure to use the aforementioned commands.







Feedback and Knowledge Base