Lesson 15 Topic 1 Features
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.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 15 :: Topic 1
When a test is executed in Worksoft SaaS, it may fail for various reasons. Below is the categorization of the most common failures in Worksoft SaaS and their reasons (This is not an exhaustive list, as the list of errors is always different for different tests).
1. Test Automation: Errors in this category occur due to poor automation design.
For example: You're building automation for an e-commerce web page where you are navigating from PLP(Product Listing Page) to PDP(Product Detail Page), you might have added validations like assert to ensure the page loaded correctly, but if the AUT is experiencing some latency issues and the page has still not loaded, then the assert validation will fail the test. It is recommended that you add some 'wait time' to AUT to load completely by adding commands like Settimeout.
2. User Errors: Errors in this category occur due to improper usage of features in Worksoft SaaS
Example: When executing tests, you might have selected incorrect data file or data filter, or mistakes during parameterizing the data, etc.
Another example is when any test run is in Queued/In-Progress state and if you have accidentally clicked on the abort icon, then the test execution is aborted or canceled.
3. Application Defect: Errors in this category occur if the actual results in the AUT did not match the expected results. For example: You have a test case which states what the expected result would be. You have built automation accordingly and when you execute the test, it failed because a different response was identified which does not match with the result indicated in the test case. Typically, these are the kind of errors you are looking for.
4. Application Flakiness: Errors in this category occur if the AUT shows flaky responses with each test.
This may happen when there is a load on the AUT or other system issues at the AUT end, you may see certain commands failing with timeout leading to flakiness in tests but work fine after re-run.
5. Worksoft SaaS Flakiness: Errors in this category occur if the AUT shows flaky responses with each test.
This may happen when performing tests on the cloud, at times browser may be slow or stop responding or other issues like some components at Worksoft SaaS end might not respond initially but work fine after re-run.
6. Capacity: Errors in this category occur if the subscription purchased by you has a capacity allocation (Domain/Project/Product/user) that has exhausted. Let's say you have 4800 mins of daily capacity based on your subscription and on a particular day if all available minutes were consumed and then you have few more tests which are in 'In-Progress' and/or in 'Queued' state, then they will be aborted/canceled.
1. Test Automation: Errors in this category occur due to poor automation design.
For example: You're building automation for an e-commerce web page where you are navigating from PLP(Product Listing Page) to PDP(Product Detail Page), you might have added validations like assert to ensure the page loaded correctly, but if the AUT is experiencing some latency issues and the page has still not loaded, then the assert validation will fail the test. It is recommended that you add some 'wait time' to AUT to load completely by adding commands like Settimeout.
2. User Errors: Errors in this category occur due to improper usage of features in Worksoft SaaS
Example: When executing tests, you might have selected incorrect data file or data filter, or mistakes during parameterizing the data, etc.
Another example is when any test run is in Queued/In-Progress state and if you have accidentally clicked on the abort icon, then the test execution is aborted or canceled.
3. Application Defect: Errors in this category occur if the actual results in the AUT did not match the expected results. For example: You have a test case which states what the expected result would be. You have built automation accordingly and when you execute the test, it failed because a different response was identified which does not match with the result indicated in the test case. Typically, these are the kind of errors you are looking for.
4. Application Flakiness: Errors in this category occur if the AUT shows flaky responses with each test.
This may happen when there is a load on the AUT or other system issues at the AUT end, you may see certain commands failing with timeout leading to flakiness in tests but work fine after re-run.
5. Worksoft SaaS Flakiness: Errors in this category occur if the AUT shows flaky responses with each test.
This may happen when performing tests on the cloud, at times browser may be slow or stop responding or other issues like some components at Worksoft SaaS end might not respond initially but work fine after re-run.
6. Capacity: Errors in this category occur if the subscription purchased by you has a capacity allocation (Domain/Project/Product/user) that has exhausted. Let's say you have 4800 mins of daily capacity based on your subscription and on a particular day if all available minutes were consumed and then you have few more tests which are in 'In-Progress' and/or in 'Queued' state, then they will be aborted/canceled.