Soft audit Checklist・No14: Test management technology (1/2)
- 1. We will introduce the check items of the software development audit checklist in order.
- 2. The second of the three elements of software development technology is test confirmation.
- 3. Check items related to test management check planning and actual tracing and defect management
- 4. It’s getting a little longer, so I’ll write more in the second half of the article.
We will introduce the check items of the software development audit checklist in order.
Software development auditing is an auditing method that Gutara’s father arbitrarily named to determine the capabilities of software development contractors. Overview of software development audit and pre-preparation of the audit at the time and the work of the audit on the day for, have been introduced in other articles. Also, please refer to another article for the points when using the audit checklist used in software development audits .
In the articles before and after this, we will introduce each item of the following four types of soft audit checklists in order.
- Development process checklist
- Checklist of requirements management for the first development technology
- Checklist for the second test of the developed technology
- Third design and implementation checklist for development technology
In this article, following the development process checklist introduced in the previous article, we will introduce each check item for the first requirements management checklist of development technology. The points when using the requirements management checklist are introduced in the article on software audit practice / audit day 9: test technology check points , so I think it will be easier to understand if you read that as well. increase.
The second of the three elements of software development technology is test confirmation.
In this article, I will introduce the second test checklist for software development technology . In software development technology , requirements management at the entrance to development is the most important and the second most important is testing . Even if the requirements management of what to make is done properly, it will not be good software unless the software is made properly according to the requirements.
Testing is a direct way to make sure that your software meets your requirements . In the test, in addition to confirming the functional requirements that the functions are built according to the requirements , it is confirmed that the non-functional requirements such as performance, responsiveness, reliability and robustness are also made according to the required specifications. need to do it. We will confirm by software development audit whether such a test process is done properly.
Like other checklists, this checklist does not have any rules or standards because the software development audit is a mechanism created by Gutara’s father. It’s just that Gutara’s father made and used this kind of thing without permission . Even so, I think it can be used as a reference for judging development skills related to testing of development contractors. I will post it here, so please read the article while referring to this list as well.
Test checklist
(click to open pdf)
The test checklist also has one check item per line, and there are six columns in the horizontal direction. The usage of the six columns is the same as the checklist of the development process, so how to use each column , source of the previous article shift the auditing practices checklist Part 1: development process (requirements management) please visit.
The test checklist is divided into the following two major items, and ID numbers with the initials of each classification are attached.
- Test management (TM-) : Confirmation of planning and management of test work
- Test content (TC-) : Confirmation of the specific content of the test
Let’s introduce it now. It will be easier to understand if you read the article while looking at the test checklist.
Check items related to test management check planning and actual tracing and defect management
Test management mainly confirms work related to test planning and performance tracing and handling of detected defects as test results . But before that, let’s check the name and definition of the test . Test names and their definitions vary considerably from development organization to development organization. At Gutara’s father’s company, there were multiple development departments, but different departments had different definitions even with the same integration test name. This is the case within a single company, so different companies and even different countries often have different test names and definitions from their own .
Therefore, the first half of the check items related to test management is mostly confirmation of the test name, definition, and purpose. In the second half of the check items, there will also be confirmation items regarding the test plan and partly the quality of the test. Let’s introduce the items in order.
[Item number: TM-01]
First, check the name of the test to see what the name of the test is being done by the outsourced company . Whether you’re using the common unit test, integration test, systest, or validation test names, or a different test name, first check the name of the test your company uses . Next, ask them to be as specific as possible about the definition of the test for each name . We will confirm the definition of the test by asking what the test is intended to confirm , who will perform the test , who is responsible for the test, and so on.
[Item number: TM-02]
Now that TM-01 confirms the names and definitions of the tests used by the outsourced company, it’s time to sort out how those tests relate to general test objectives . Father Gutara uses the term test category because the purpose of the test is, from a slightly different point of view , also the type of test . For example, test category that test if the function test to verify the functionality, test category that the performance test if to confirm the performance, so that kind every minute for testing purposes those poppy, is called the test category.
And Father Gutara uses 16 test categories, which are 15 test categories in The Art of Software Testing written by Glenford Myers in 1979 plus one category called Long run test. By organizing the tests belonging to these 16 types of test categories in association with the test names used by the outsourced company, it is possible to find out what purpose test is being performed with which name .
[Item number: TM-03]
Ultimately, testing is the only guarantee of software quality. Therefore, it is very important to make sure that the necessary and sufficient quantity and quality tests are performed. There are various names of tests, but as a test to guarantee the quality of software, the system test and validation test located at the end of the test plan are important.
Therefore, we will focus on the system test and the validation test to check the amount of tests . There is no particular rule as to what the amount of test should be expressed, but the easiest to understand is the man-hours ( man-hours ) of the person in charge required for designing and executing the test and the number of test items . Divide those values by the scale of the software , convert them to test density, and then compare them with similar products of your company to determine if the amount of tests conducted by the contractor is insufficient. Information is available.