& Amp; #65279; & amp; #65279; & amp; #65279; & amp; #65

This is a technical metric for measuring whether the C/C ++ unit testing tool is competent for the actual project based on years of experience. It is for the reference of friends who need to evaluate the unit testing tool. 1. Automatic isolation test target. you can set the specified file as the test target based on the test task. B. for files that are not tested but may be heavily dependent, you can set them to call the actual code. c. for Files Not a and B, the pile code is automatically generated. 2. automatically generate test code. automatically generate test files and code frameworks required for testing; B. automatically generates test classes and test functions for each class and function. c. you can generate the corresponding Input and Output code based on the specified data. 3. Automatic table formatting a. You can move data to a table by double-clicking or similar simple operations. B. You can create, delete, and edit use cases in the table. 4. Solve testability problems. you can directly set the return values, output parameter values, and global variable values modified by the underlying function in the use case. B. you can set the value of local variables in the use case. c. data Set by a and B can be moved to the table and edited and managed with other data; d. you can determine whether the calculation result of a local variable meets the expectation. 5. White Box Coverage a. automatically calculates the following coverage rates: statement coverage, condition coverage, branch coverage, C/DC, MC/DC, and path coverage. B. unoverwritten logical unit labels are clear: unoverwritten statements, condition values, judgment values, MC/DC are marked in the Code; the logical structure of the program is automatically drawn, indicates the branch and path that are not covered. C. provides the function to help identify missing use cases. For example, for a specified uncovered unit, the system automatically calculates the most recent use cases from the existing use cases and provides modification tips or similar functions, to solve the problem that it is difficult to achieve high-standard coverage. 6. Automatic Use Case a. automatically generate a boundary test case to detect extreme errors such as crashes and timeouts. 7. Test Report. automatically generate test report; B. the test report includes the following content: coverage data of all functions; Code of the use case, input and expected output of each use case, actual output of each use case, and case reporting error. 8. support development and testing to improve development efficiency. when the product code is modified, the test code is synchronously updated and the test is automatically executed. B. the test results intuitively describe program behavior: What is input, what code is executed under the input, and what output is generated.