Table of Contents
- 1 Which test cases should be automated which test cases are not suitable for automation?
- 2 How do you identify a test case?
- 3 How do you identify automation?
- 4 How do you identify a regression test case?
- 5 How do you evaluate candidates for automation testing?
- 6 What are the advantages of automation in software testing?
Which test cases should be automated which test cases are not suitable for automation?
Only certain types of test cases can be automated. Subjective test cases — test cases that are not testing a clear function — will still need to be done manually. Here are some examples of test cases that cannot be automated: Exploratory tests.
How do you identify a test case?
The test case should contain a set of test data, preconditions, expected results and post conditions, developed for a particular test scenario in order to verify a specific requirement. The test case should check normal happy flow, alternative flow and error flow.
Which all test cases can be automated in regression testing?
A top 8 regression testing test case checklist
- Cases with frequent defects.
- Functionalities highly visible to users.
- Cases which verify core features of the product.
- Cases of functionalities that have undergone recent changes.
- All complex and integration test cases.
- Boundary value test cases.
- A sample of Successful test cases.
How do you choose automation testing over manual testing?
Manual testing is suitable when the test cases are run once or twice. Therefore there is no frequent repetition of test cases. Automated testing is suitable when the test cases need to run repeatedly for a long duration of time.
How do you identify automation?
Identifying tasks for automation
- Involve a high degree of manual overhead.
- Are prone to manual errors.
- Have clearly defined business rules.
- Are relatively stable and mature (i.e. not expected to go through major change or redesign in the future, such as a system overhaul)
- Are centrally governed and consistently followed.
How do you identify a regression test case?
Best Practices in Identifying Test Cases for Regression Suite
- Incremental code changes in a project or a release.
- Major releases or projects going live.
- Emergency production fixes.
- Configuration and environment changes.
How do you perform a regression test in automation testing?
How to Do Automation Regression Testing
- Software change analysis — at this stage a developer estimates which system component will be changed as well as the extent of the change.
- Software change impact analysis.
- Building a regression testing strategy.
- Creating a test suite.
- Executing regression tests.
- Reporting.
How to choose the right test cases for automation?
With that being said, there are some crucial factors upon choosing automation test cases that testing teams must consider: Execution time and testing frequency of the test cases: if the answer to both components is significant, these test cases make a strong candidate for automation.
How do you evaluate candidates for automation testing?
Identify the parameters on which you will evaluate candidates for automation testing. Then, teams can break the AUT into module test cases and measure that against the criteria above. Before finalizing your selection, perform an ROI measurement as the last filter, and as criteria for automation results.
What are the advantages of automation in software testing?
There are many advantages of automation; here are few important to mention: Useful to execute the routine tasks like smoke tests and regression tests. Useful in preparing the test data. Helps to execute the test cases which involve complex business logic. Good to execute the cross-platform test cases (like different OS, browsers etc.)
What is test case in software testing?
In software testing, a test case is a detailed document of specifications, input, steps, testing conditions, and expected outcomes regarding the execution of a software test on the application under test (AUT).