[Tool] 22 test types to be considered in the test design

22 types of software testing to be considered in the test design

Black box testing: not based on any knowledge of internal design and code, but on requirements and functionality.

White-box testing: based on the internal logic knowledge of an application code, testing is based on covering all code, branches, paths, and conditions.

Unit test: a minimal test to test a function or code block. Typically, programmers rather than testers need to know the details of internal program design and coding. This work is not easy to do unless the application system has a well-designed architecture; you may also need to develop test drive modules or test kits.

Cumulative comprehensive test: continuous test performed on the application system when a new function is added. It requires that the different forms of functions of the application system be independent enough to work separately before the completion of all systems, or those test drives have been developed when necessary; such tests can be performed by programmers or testers.

Integration testing: joint testing of each part of an application system to determine whether they can work together. Parts can be code blocks, independent applications, clients on the network, or server programs. This type of test is especially related to the client server and distributed system.

Function testing: a black box testing method used to test the functional requirements of an application system. This type of testing should be done by the tester, which does not mean that the programmer does not have to check whether their code can work before release (naturally, it can be used for various stages of testing ).

System testing: black-box testing based on the overall requirement specification of the system; all components associated with the system should be covered.

End-to-end testing: Similar to system testing, the test-level "grand" endpoint, and all tests that involve simulated situations when the entire application system environment is used in a real world. For example, talking to a database, communicating over the network, or talking to external hardware, application systems, or appropriate systems.

Sound testing: typically refers to an initial test to determine whether a new software version test is sufficient to perform the next big test effort. For example, if a new version of software conflicts with the system every five minutes, causing the system to get stuck, it means that the software is not "sound" and is currently not qualified for further testing.

Failure testing: software or environment repair or corrected "retest ". It may be difficult to determine how many times a test is required. Especially when the development cycle ends. Automated testing tools are especially useful for such tests.

Acceptance test: a final test based on the specifications of the customer or end user, or based on the use of the user for a period of time, to see if the software meets the customer's requirements.

Load testing: tests the performance of an application under heavy loads. For example, tests a Web site under heavy loads when the system response degrades or fails.

Force testing: a term often used for alternate load and performance tests. It is also used to describe tests such as system function tests under unusual heavy loads, such as a certain action or a large number of input duplicates and a large amount of data input, A large number of complex queries are performed on a database system.

Performance testing: a term commonly used for alternate load and force testing. Ideal "performance tests" (and other types of tests) should be defined in the requirement document or quality assurance, test plan.

Usability testing: user-friendly testing. Obviously this is subjective and will depend on the target end user or customer. User interviews, surveys, user dialogs, and other technologies are available. Generally, programmers and testers are not suitable for usability testers.

Installation/uninstall test: test the software installation/uninstall process in full, in part, or during upgrade.

Recovery Testing: test whether a system can be well recovered from the following disasters, such as system crashes, hardware damages, or other catastrophic problems.

Security testing: tests how the system prevents unauthorized internal or external users from accessing or intentionally damaging the system. This may require complex testing techniques.

Compatibility testing: tests the performance of software in a specific hardware/software/operating system/network environment.

Comparison test: a comparison test with a competitor's products, such as software weaknesses, strengths, or strengths.

Alpha test: test the application system when system development is nearing completion. After the test, there will still be a small number of design changes. Such tests are generally completed by end users or other personnel and cannot be completed by programmers or testers.

Beta testing: tests performed when development and testing are complete, and the final errors and problems need to be found before the final release. Such tests are generally completed by end users or other personnel and cannot be completed by programmers or testers.

[Tool] 22 test types to be considered in the test design