Senior test veteran finishing, detailed explanation of super fully automated test cases-summary of tips...

Contents: Guide

foreword

Python automated testing: https://www.bilibili.com/video/BV16G411x76E/

Before starting automated testing, you need to see what benefits automation testing can bring after considering the time, effort, and resources invested in it.

Here are the questions you should consider to determine which manual tests should or should not be automated.

Automated tests that should be done

①Business critical path: If a function or user action fails, it will cause damage to the business;
②Tests that need to be run for each build/release of the application, such as smoke testing, sanity testing and regression testing;
③Required Tests that run against multiple configurations (different OS and browser combinations);
④ tests that perform the same workflow use different data as input in each test run, such as data-driven;
⑤ tests that involve inputting large amounts of data, such as Filling out very long forms;
⑥ tests that can be used for performance testing, such as stress tests and load tests; ⑦ tests
that take a long time to execute, and may need to be performed during breaks or overnight;
The behavior of the application is as expected, or check that multiple web pages on multiple browsers look the same;
⑨In general, the more repetitive the test runs, the better for automation;

Also remember that test case automation is not the only option for automation. Tasks like setting up or creating test data for manual exploratory testing are also ideal ways for automation to demonstrate its value.

Automated tests that should not be done

① The test can only be run once. The only exception to this rule is that if you are going to perform the test with a very large data set (even just once), then it makes sense to automate it
; response);
③ tests that need to be run as soon as possible. Usually, new functions developed require quick feedback, so please give priority to manual testing;
④Tests that require temporary/random testing based on domain knowledge/expertise are exploratory tests;
⑤Intermittent testing. Testing without predictable results leads to more uncertainty. In order to get the most value from automation, tests must produce predictable and reliable results in order to produce strict pass and fail conditions; ⑥
tests that require visual confirmation, however, we can capture page images during automated testing and then manually inspect them Image;
⑦ Tests that cannot be 100% automated should not be automated at all, unless doing so will save a lot of time;

Summary: Simplicity > Priority > Stability > Repeatability.

Tips for Automating Test Cases

Software testing automation has many advantages over manual testing. It improves results and quality, increases reliability, and reduces bias in results.

Additionally, it speeds up the process, increases coverage testing and ultimately improves the overall quality of the software. Good automation improves delivery quality, increases testing coverage, reduces testing cost, and enables early detection of bugs when proper testing is done.

1. Repeat the test
This is the golden rule. If test runs are repetitive, they should be automated. This saves you valuable time and energy. Also, if this is a test that you assume will be run frequently in the future, automation is a great way to go. Get faster and more accurate results every time.

2. High-difficulty test cases
If a test case has a high risk of errors and destruction during human execution, or manual testing is difficult to complete, automated testing should be used first. If the risk involved is high, then this test case should be automated.

3. Main process use case
It is a very good practice to automate the main process use case of the application. Avoid any possibility of human error and be safe and fast. For test cases that may endanger the entire project, automated testing should be prioritized.

4. Wide range of use cases
Scenarios that require a large amount of data and conditional testing are more suitable for automated testing. Also, chances of making mistakes during manual testing may increase. This is an important reason why testing usually uses a test-driven model, and we mainly refer to those test cases that require more forms to be filled.

5. Assess the pros and cons
by evaluating the time required to complete the automated process or conduct the test manually. If some projects are not suitable for investing time in automated testing, the automated testing process itself takes more time than manual testing, indicating that automation is not worth it.

6. Three golden tests
When it comes to automation, there are three test cases that should not be questioned: regression testing, smoke testing, and sanity testing. Why? Because every build or release of the app needs to be tested.

7. Complex cases
Many test cases need to set a lot of preconditions, and the setting of these preconditions is usually more complicated. Such use cases need to be automated first, because it can save a lot of time, even if it is only for functional testing Do some automated scripts.

8. Long-term testing
If the test case spans a long time, usually more than ten minutes or several hours, it should be automated.

The following is the most complete software test engineer learning knowledge architecture system diagram in 2023 that I compiled