- This topic has 2 replies, 3 voices, and was last updated 4 months, 1 week ago by .
- You must be logged in to reply to this topic.
In what condition we cannot use automation testing for the agile method?
ASP.Net Software Development
It’s important to know when and when not to automate tests, JoEllen said that if a test is only performed once then it shouldn’t be automated. “One-time tasks and exploratory testing/edge cases shouldn’t be automated. Edge cases are, by definition, usually one-off test cases, and the effort to automate edge cases generally does not pay off.
Test automation is a fundamental part of Agile, but there are certain times where automation testing in agile is useless, like:
When there is an exhaustive level of documentation
When the requirements keep changing
One-time tasks and exploratory testing cases shouldn’t be automated
I recently came across a platform called QAppAssure which allows you to test on-cloud and on-field devices, across 100+ device, make and models, Integrate with Jira, CI/CD tools, and also use Appium, Calabash, Espresso, UI Automator, XCUITest. You can run unlimited parallel tests with the free trial pack.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.