Software acceptance testing is a commonly used testing method in the software testing industry, so what testing content needs to be included in the acceptance test?
1. Review of software product specifications
Conduct audit work from the customer's perspective and standpoint. Check the correctness of the applied standards and do not conflict with industry norms. Review and research similar products. Verify the completeness, accuracy, consistency and rationality of product specifications.
2. Verification of software product specifications
(1) The realized features are marked as passed;
(2) The feature is not implemented, report the bug and reflect in the report;
(3) The feature is basically realized, but it is inconsistent with the content of the product manual, report a bug and reflect it in the report;
(4) The features are basically realized, but there are some problems or errors.
3. User interface and usability testing
(1) The 7 elements of the user interface: compliance with standards and specifications, intuitiveness, consistency, flexibility, comfort, correctness, and practicality;
(2) The usability test has no specific quantified index and is highly subjective.
4. Compatibility test
(1) Software compatibility testing refers to verifying whether the software interacts and shares information correctly;
(2) Compatibility includes: hardware compatibility, software compatibility, and data compatibility.
5. Installability and recoverability test
Installability test: system software installation, application software installation, server installation, client installation, product upgrade installation, etc.
Recoverability test: Recovery test mainly checks the fault tolerance of the system. When an error occurs in the system, can the error be corrected or the system restarted within a specified time interval? The recovery test must first use various means to force the software to trigger a fault (BUG), and then verify whether the system can be recovered as soon as possible.
6. Document testing
Software documentation has become an important part of the software, and there are many types, and the testing of the documentation has become essential.
Types of documents: online help documents or user manuals; guides and wizards; installation and setup guides; examples and templates; error messages; images and sounds for demonstration; authorization/registration forms and user license agreements; software packaging, Advertising materials, etc.
7. How to conduct document testing
(1) Good documentation needs to achieve the purpose of improving ease of use, improving reliability, and reducing technical support costs, thereby improving the overall quality of the product.
(2) Non-code document testing mainly checks the correctness, completeness and comprehensibility of documents.
8. What good third-party software testing company recommends?
Companies need to do software testing, and can't find a suitable software testing agency all at once? You can learn about ZhuoMa software testing and evaluation. It has a professional testing team, mature testing technology, rich experience, and thoughtful service. It can provide various software testing services and issue reliable third-party software testing reports.