Mobile APP testing-how to specify testing strategy and testing standards?

• Developing a project testing strategy is an important step that can help the testing team clarify testing objectives, testing scope, testing methods, testing resources, testing risks, etc., thereby improving testing efficiency and quality.
• This article is a summary of some experiences and theoretical sharing. It is not absolutely correct, and everyone is welcome to discuss it.

1. Contents of testing strategy

• The testing strategy includes the following aspects:
  • Testing level : refers to testing software at different levels according to different stages of the software development process, such as unit testing, integration testing, system testing, acceptance testing, etc.
  • Roles and responsibilities : This refers to the need to clearly define each role and the responsibilities of that role in the testing strategy. For example, project managers, test team leaders, test engineers, etc.
  • Environmental requirements : refers to describing the system environment required for testing, including software, hardware, network environment, etc.
  • Risk analysis : refers to identifying and evaluating various risks that may affect the quality and progress of the test, and formulating corresponding countermeasures.
  • Test progress : refers to formulating a reasonable test schedule based on the project plan and resource arrangement, and monitoring and controlling the execution of test activities.

2. The process of specifying testing strategies

• The general process for developing a testing strategy is as follows:
  • Analyze the product : Understand the product's features, functions, needs, users, market, etc. to gain a deeper understanding.
  • Develop test strategies : Based on product analysis, create test strategies for different test levels, determine test focus and difficulties, test depth and breadth, test methods and technologies, etc.
  • Specific test goals : List all software features (function/performance/GUI) that may need to be tested, and define corresponding quality indicators and acceptance criteria.
  • Define testing standards : Develop standards or rules for judging various indicators during the testing process, such as defect level, defect status, defect closing conditions, etc.
  • Resource Arrangement : Based on the project plan and resource situation, determine the amount of manpower, equipment and materials to be used in the project, and reasonably allocate tasks and responsibilities.
  • Test environment : Describe the system environment required for testing, including software, hardware, network environment, etc., and ensure that it is consistent with or close to the actual user environment.

3. Develop test standards (test scope, standards)

• Developing test standards is an important part of the testing strategy.
• The test scope and standards shared below come from the experience summarized in my work.
• However, the characteristics of each project are different, and the most appropriate standards and scope need to be formulated based on the characteristics of the project.

1. new product testing
   • This type of product is the first to be launched online. Theoretically, all codes for this type of product are brand new and untested, so the test standard is: all functions of the product pass 100% of the forward process and 20% of the reverse process.
2. Version iteration testing
   • The difference between this type of testing and new product testing is that the product already has an online version, and this version is developed based on the previous version. Therefore, the test focuses on newly added code and changes to the original code. And special attention should be paid to covering the installation situation, so the test standard is: the new code and the affected code pass 100% of the forward process and 20% of the reverse process. And the core functions of the product must also ensure that there are no abnormalities in the forward process, such as login functions and payment functions.
3. Bug fix testing of the same version
   • Sometimes it is necessary to launch a version of the same version that fixes crashes or bugs after collecting data without adding new business functions. For this type of testing, if it is to fix a visible bug, you need to verify whether the bug has been fixed. If it is an invisible bug, it is a normal test of the core functions of the product. Therefore, the test standard is: verify that the bug has been fixed (when the bug is visible), and the relevant functions are near the location where the bug occurred. There is no abnormality in the forward process of the core functions of the product.

• Note: All test standards are theoretically: no bugs within the specified test range. However, there are bugs in actual production work that cannot be fixed before the project deadline, or the cost of bug fixing is greater than the benefits brought by bug fixing. Therefore, when encountering this situation, we will evaluate together with the planning and development to determine whether the bug needs to be fixed. If all three parties pass, there may be cases where the bugs are not completely fixed and the test will end and the product will be launched.

—————————————————————————————————————————————————————————————————————————————————————————————————
I am a blog of myself. No. [Essential Skills for Software Testing] will upload testing related information from time to time. You can click on the QR code below the article to get it~