Test plan・The plan writes the test policy first　

12/04/202120/10/2021Test qualityy

Software test plan is a test of the policy in the first write

The first thing to think about when creating a software test plan is the testing policy . This is because the specific content of the test , such as the purpose of the test to be conducted, the test schedule, the man-hours to be input, and the schedule , will be decided according to the test policy . It is also important to write the test policy at the beginning of the test plan so that the entire test team can recognize the test policy and design and execute a concrete test.

The test policy is the important point in the test.

By the way, what is the test policy? In other words, the test policy is important in the test . This is still abstract and I’m not sure, but if I try to write down what is important in the software tests that Father Gutara has seen so far, it will be as follows. This is an example of a test of the policy is.

1. Emphasis on completeness of function / performance confirmation
2. Emphasis is placed on checking compatibility of functions and performance
3. Emphasis on confirmation of RAS function
4. Focus on the efficiency of test work
5. Emphasis on validation
6. Emphasis is placed on checking for secondary defects

Testing purposes of the software, in either quality assurance quality improvement of the tested software (up bugs) (confirmation of that there is no bug), any point with an emphasis in the test listed above, among the items necessary for the test It’s just one of them. However, deciding what to prioritize among those items is, in other words, which item should be given priority when testing with limited time and equipment. It means to decide what it is and put it.

The important points in the test depend on the purpose of the software.

What determines what is important in the test, and in fact , what is important in the test depends on the purpose of the software to be released . For example, if the software is released when a new product is released, the comprehensiveness that all functions work is emphasized first, and if the software is a bug-fixed version, the impact confirmation of the secondary defect is emphasized. From that point of view, let’s think a little more about what kind of software the items listed above should be emphasized when releasing.

Emphasis on completeness of functions and performance when the first edition of a new product is released

If it is the first edition software that will be installed when the new product is released , it is at least necessary that all the functions work properly and the required performance is obtained. Of course, there are other important items as software such as stability and maintainability compatibility, but it is most important that the functions and performance are properly completed when a new product is released. To confirm this, it is important to confirm the completeness of functions and performance , and this is the test policy.

Emphasis is placed on checking compatibility of functions and performance when the revised version or the second version is released.

When releasing the second version of the software by adding functions after a while after the new product is released, it is certainly important to check the functions and performance of the new functions. However, if the software is the second edition of a product that already has users who are already using the first edition in the market, it is more important to check the compatibility of functions and performance with the first edition so that existing users can use the second edition smoothly. Will be. If the function or performance is improved, there is no problem because it is okay to change from the first edition, but it is a problem if the function or performance deteriorates.

Emphasis is placed on confirming the RAS function in upstream equipment and devices

In the case of software installed in equipment and devices that make up the most upstream system for providing services , such as in the center or cloud, rather than the devices used by end users, stability, availability, and availability are more important than functions and performance. The so-called RAS function of maintainability becomes more important. It is of utmost importance that the equipment and devices in the center and cloud continue to operate stably 24 hours a day, 365 days a year in order to provide zero difference . This is the most important item because the RAS function is important for that purpose.

Emphasis on streamlining test work for products that are released frequently

There are various ways of thinking about software release. For example, in the case of software for a system that cannot tolerate mistakes, such as a financial system, we will release the software after thoroughly testing it to ensure sufficient quality. On the other hand, for terminals operated by end users, such as Windows, which is the OS of personal computers, there is also a release method in which the quality is rapidly improved after the release by frequently issuing bug fix patches even after the release. I have.

When taking the form of release like the latter, it is important to complete many tests in a short period of time because the interval between releases is short . Therefore , it is sometimes the most important to improve the efficiency of test work by making full use of test automation .

When there are many situations where it is used, emphasis is placed on validation of BtoB product software.

In the case of a product that the end user directly touches with BtoC, it is easy to test because the usage of the product can be assumed, but in the case of a product used for business use with BtoB , the product developer is specific. It may not be possible to fully understand the intended use. In such a case, no matter how much design verification is performed to guarantee the contents written in the required specifications of the software, it may be used unexpectedly in production operation and a potential bug may be discovered.

In the case of such a product, it is important to verify the design to confirm that it meets the required specifications, but to confirm the validity of the product from the viewpoint of whether it can provide the necessary services in the situation where the product is used. It is also necessary to emphasize.

When releasing a bug-fixed version of software, focus on checking the range of influence

In the case of a bug-fixed version of software that fixes a bug found on the market, the important thing in testing is to check for secondary defects due to the fix . Even though we released a bug-fixed version, if we put in other bugs, there is no source or child.

The test policy is the basis for judgment when testing with limited time, equipment and personnel.

Unfortunately, in the field of software testing, work is often continued at the last minute due to lack of time, equipment, and personnel. It’s a so-called death march state . In such a case, it is inevitably necessary to judge what to do and what to give up . It will be easier to judge if the test policy has been decided as to what is important in the test as the basis for that judgment. Therefore, write the test policy at the beginning of the test plan.

After writing the test policy on the test plan, write the test goals.

Next : Test plan・Test Goal (Part 1) Delivery time, cost and product quality

Back : Test type・Is the test for debugging or for quality assurance?　

Return to :  Testing is the only way to guarantee software quality