For Xinchuang software, it is necessary to combine its own characteristics and the actual use needs of user units to select the appropriate quality characteristic range and formulate appropriate test plans to discover adaptation problems with maximum efficiency and complete the improvement of adaptation quality as soon as possible. . So, what are the four characteristics of Xinchuang software testing quality? Now, let’s take a look at the detailed introduction!
1. Portability Test
(1)Adaptability
1. The software’s ability to adapt to different specified environments shall be confirmed through testing according to the contract and user agreement. The testing scope includes: hardware environment (such as CPU, storage, network switches, routers and other equipment), minimum configuration requirements for software operation and Recommended configuration requirements, software environment (such as operating system, database system, browser, supporting software, etc.) and data structure.
2. The environment combination must at least meet the basic selection combination (only one hardware device/software is changed at a time). If otherwise defined, the detection shall be carried out according to the definition (such as a pairwise combination or a higher combination), such as Feiteng+Tongxin+WPS, Feiteng +Qilin+Yongzhong.
(2) Easy installation
1. Design test cases to verify the effectiveness and efficiency of the system under test, such as the validity of installation documents and the degree of automation of the software installation and uninstallation process.
2. Design test cases to verify each installation option, including software installation method (custom installation, default installation, quick installation, etc.), path, user name, database, etc., and the software can be successfully installed in each case.
3. Design test cases to verify whether the uninstallation is complete according to the uninstallation instructions (automatically uninstall using the uninstall wizard, uninstalling from Add/Remove in the control panel, or directly deleting the corresponding folder, etc.); if the uninstallation is incomplete, the user needs to be prompted.
(3) Ease of replacement
Verify the replacement method of software products, including coverage, upgrade, uninstallation and reinstallation of software products, etc. Under the described circumstances, the software should be able to be successfully reinstalled or upgraded, and the data saved under the previous version will be restored in the new version. version can be used correctly.
(4) Compliance
Meet the requirements of standards, conventions, and regulations related to portability. If the software product involves meeting the portability requirements of relevant national standards, industry standards, local standards, enterprise standards, bids, letters of responsibility, contracts, product quality laws, safety production laws and other documents, Corresponding testing is required.
Portability testing should fully verify the applicable scope of the software definition and provide manufacturers and users with confidence in the use of the software. For custom systems, portability testing should be done as early as possible. If the version of the operating system, browser, etc. is not specified, the version of the current mainstream domestic product should be verified.
If data migration between the old and new systems is involved, a complete analysis of the data differences between the old and new systems should be made, clear methods for handling unmapped fields, and adequate testing of data backup, data cleaning and conversion, migration tools, data verification tools, system switching plans and emergency measures. .
2. Compatibility testing
(1)Coexistence
After the software is installed and configured according to the requirements of the user documentation set, the degree to which the product can effectively perform its required functions without negatively affecting other products under the condition of sharing the common environment and resources with other software. Mainly observe whether the CPU, process and other system resources of the operating system are abnormal, or cause other software operation errors (such as mutual exclusion of anti-virus software) or the software's own function implementation errors, or system errors, unfriendly interface display, etc.
(2)Interoperability
If it involves user-invokable interfaces and related software to be invoked, the type and length of data or streams, etc., test the ability to work together to complete a function, such as supporting import/export of .xls, .doc files, XML, images Collection equipment, etc.
(3) Compliance
Meet the requirements of standards, conventions, and regulations related to compatibility. If the software product involves meeting the compatibility requirements of relevant national standards, industry standards, local standards, enterprise standards, bids, letters of responsibility, contracts, product quality laws, safety production laws and other documents, it must Carry out corresponding tests.
During the test, on the domestically produced mainstream chip routes and operating systems, it was checked that the software was compatible with the system and could run simultaneously with other software when running in the system. It involves collaboration and the ability to complete and use correct data exchange. These tests can also be combined with functionality for test execution.
3. Functional testing
(1)Integrity
1. Test the extent to which the actual functions of the software cover all functions to be implemented. If there are requirements documents referenced in the product description, the software should be checked to meet all requirements of the relevant documents. Also pay attention to implicit requirements. For a ready-to-use Xinchuang software system, the basic functions that users need to use are complete, and administrators can implement basic system management. Pay attention to discover whether there are any deletions of key functions due to technical implementation obstacles in the adaptation.
2. Self-contradictions that should not occur in the software include contradictions in operation, contradictions in expression (such as contradictions in the expression of text and graphics), etc.; all features mentioned in product descriptions and user documentation should be consistent with the software. These characteristics include functions, operations, input/output constraints, etc.
(2)Suitability
1. The realization of functions meets the goals. The software should be able to use the corresponding environmental facilities, equipment and data to achieve its stated functions within the restricted scope and environment required by the user documentation set. Verify that end users control and operate the software according to the guidance of the user documentation set and should be able to successfully complete specified tasks.
2. Check whether the operation steps are reasonable and there are no fatal or serious problems that affect the experience. Functions should be based on task characteristics, not on the technology that implements the task. Pay attention to discover whether there are bugs or redundant steps in the adaptation caused by technical difficulties in the adaptation.
(3)Correctness
1. When executing input and output test cases, the actual output should be consistent with the expected output.
2. The output results and output accuracy of the software should meet relevant requirements. (Such as maximum and minimum input value requirements, password length requirements, precision requirements for floating point numbers, precision requirements for percentage calculations, bit error rate requirements for data transmission, etc.)
(4) Compliance
Meet the requirements of standards, conventions, and regulations related to functionality. If the software product involves meeting the functional requirements of relevant national standards, industry standards, local standards, enterprise standards, bids, letters of responsibility, contracts, product quality laws, safety production laws and other documents, it must Carry out corresponding tests.
Functional testing is mainly black box testing, and common testing methods such as equivalence classes, boundary values, scenario testing, cause-and-effect diagrams, and error speculation can be used.
4. Performance efficiency test
(1) Time characteristics
1. Test response time: the time elapsed from when the user initiates a request to when the server completes processing the request and returns the processing result.
2. Test processing time: database query time, transaction processing time
3. Test throughput rate: TPS, RPS, network throughput traffic
(2) Resource utilization rate
1. Monitor server resources: CPU, memory, IO, bandwidth, etc.
2. Monitor database resources: data buffer, hit rate, connection pool, TPS, etc.
(3)Capacity
Test capacity: the maximum limit, that is, the upper boundary. Maximum number of concurrencies, maximum number of data records, maximum file length, maximum bandwidth, etc.
(4) Compliance
Meet the requirements of standards, conventions, and regulations related to performance efficiency. If the software product involves meeting the performance and efficiency requirements of relevant national standards, industry standards, local standards, enterprise standards, bids, letters of responsibility, contracts, product quality laws, safety production laws and other documents, it must Carry out corresponding tests.
The above is the article content compiled by Guangzhou Palm Intelligent Technology for everyone. I hope it will be helpful to you. If you need Xinchuang testing software later, you can directly consult our customer service online.