Performance Testing :: Module 3 :: Topic 5.4 :: Updating scripts to capture errors and control executions( Read)
This article is a part of the Self-paced Learning Series for the Course: Performance TestingPlease refer to the link for more details on the Course.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 5 :: Topic 5.4
1. Commands for Exception handling
Apart from what we added until now, we can also implement exception to receive emails for critical failures of tests. For example, consider 404 error. After launching performance test with 500 concurrency and most of the tests are failed, After debugging the tests we got to know that, the failures are due to 404 page not found error. If this happens freqient times, the infrastucture, time will be of waste and performance testing will not be achieved. To avoid this, we can implete exception and email features of worksoft saas, so that after 10 occurences of 404 error, we can choose to abort the entire test with which we can save the minutes(which represent actual money).
Similarly we can set mutliple configurations to control the batch and receive notifications whenever needed. Please be noted that this should be identified in design phase and should be developed as part of test scripts by which it saves the time, else updating entities after completing automation takes duplicate work and time consumption.
Similarly we can set mutliple configurations to control the batch and receive notifications whenever needed. Please be noted that this should be identified in design phase and should be developed as part of test scripts by which it saves the time, else updating entities after completing automation takes duplicate work and time consumption.