Software Testing Basics (iv) test types

Installation test

The test is installed to ensure that the software is properly installed and running on the customer's hardware device.

Compatibility test

A compatibility test is a test that tests the software on a particular hardware platform, between different application software, on a different platform, on a different network, and in a very friendly environment. The main core content is 1) to test whether the software can be compatible on different operating system platforms, or whether the software can be compatible on different versions of the same operating platform, 2) whether the software itself is forward or backward compatible, 3) whether the test software is compatible with other related software, and 4) data compatibility test, mainly refers to the data can be shared.

Sound test and smoke test

Sanity testing is a simple test of the main function to determine whether the system can continue further testing. Generally refers to an initialized test work to determine whether a new software version is sufficient to perform the next test case. For example, if a new version of the software conflicts with the system every 1 minutes, causing the system to crash, stating that the software is not "sound", and currently does not have the conditions for the next test.

The smoke test object is every newly compiled version of the software that needs to be formally tested to verify that the software is functioning properly and that it can perform the following formal testing work. The performer of the smoke test is the version compiler.

Regression test

Regression testing refers to re-testing the old code after it has been modified to confirm that the modification did not introduce a new error or cause other code to produce an error. Automated regression testing significantly reduces the cost of system testing, maintenance upgrades, and more. As an integral part of software life cycle, regression testing occupies a great proportion of workload during the whole software testing process, and many regression tests are carried out at every stage of software development. In progressive and fast iterative development, successive releases of new versions make regression testing more frequent, and in extreme programming methods, it is required that several regression tests are performed every day. Therefore, it is very meaningful to improve the efficiency and effectiveness of regression testing by choosing the right regression test strategy.

Acceptance Testing

Tests typically performed by the customer in their own environment (UAT). As a test type (non-test phase), it may also be intended for the delivery of software between two different organizations and departments.

Alpha Test (alpha test) and beta test (beta test)

Alpha testing refers to the software development company organization internal personnel simulation of various types of user lines to the upcoming software products (called Alpha version) testing, trying to find errors and correction. The key to alpha testing is to simulate as realistically as possible the actual operating environment and the user's operation of the SOFTWARE product and to do its best to cover all possible user operations. Software products that undergo alpha-test tuning are called beta versions.

Beta testing is a test performed by multiple users of the software in a real-life environment, and these users return information about the error to the developer. When testing, developers are usually not on the test site. As a result, beta testing is a software field application that can be performed in an environment that is beyond the developer's control. In beta testing, the user notes all issues encountered, including real and subjective, and reports to the developer on a regular basis. Beta testing primarily measures product Flurps, focusing on product support, including documentation, customer training, and support for product productivity. Beta testing can only begin if the alpha test reaches a certain level of reliability. It is in the final stages of the entire test. At the same time, all manuals for the product should be fully finalized at this stage.

Functional Testing

Functional testing is to verify the function of the product, according to the function test case, test it by item, check whether the product meets the user's requirement function. Functional testing is also called black-box testing or data-driven testing, just consider the need to test the various functions, do not need to consider the entire software internal structure and code. Generally from the SOFTWARE Product interface, architecture, according to the requirements of the test case, the input data between the expected results and the actual results of the evaluation, And then put forward more to make the product meet the requirements of user use.

Destructive Testing

Destructive testing is a test to make a system or subsystem crash. It often tries to provide some illegal input to the system in an attempt to make the system crash for testing purposes.

Performance testing

The performance test simulates various normal, peak, and abnormal load conditions through automated test tools to test the system's performance indicators. There are three kinds of performance tests: Stress test, load test and capacity test.

Load test A main purpose of testing software system to meet the requirements of document design objectives, such as software in a certain period of time, the maximum number of concurrent users supported, software request error rate, etc., testing is the performance of software systems.

Strength testing is also a stress test, the pressure test is mainly to test whether the hardware system to meet the requirements of document design performance objectives, for example, in a certain period of time, the system's CPU utilization, memory usage, disk I/O throughput, network throughput, stress testing and load testing the biggest difference is the test purposes are different.

Capacity testing is to determine the maximum amount of system withstand, such as the maximum number of users, maximum storage capacity, the most processed data traffic.

Ease of Use testing

Usability testing is to test whether the system is easy to understand and use, mainly from the perspective of the use of the program.

Security testing

Security testing is the process of testing a product to verify that the product complies with the security requirements definition and product quality standards during the life cycle of the IT software product, especially when the product development is basically completed to the release stage.

Internationalization and Localization Testing

The goal of internationalization testing is to test the internationalization support ability of software, to discover the potential problems of internationalization of software, and to ensure that the software can operate normally in different regions of the world. Internationalization testing using each of the possible international input types, checking the functionality of the product for any culture or locale, the software internationalization test focuses on executing international string input/output functions. Internationalized test data must contain mixed characters in East Asian, German, complex script characters, and English (optional).

Localization is the change in the software version language, such as Windows, which changes English windows to Chinese, is localized. The localization test object is a localized version of the software. The goal of localization testing is to test the quality of software localization for a specific target locale. The environment for localization testing is to install localized software on localized operating systems. From the test method can be divided into basic functional testing, installation/uninstallation test, local area of the software and hardware compatibility test. The content of the test mainly includes the interface layout after software localization and the language quality of software translation, including software, documentation and online Help.

A/ b Test

Using A/B testing first needs to establish a test page (Variation page), which may be in the title font, background color, wording and other aspects of the original page (Control page), and then the two pages in a random way to all browsing users. The next two pages of the user conversion rate, you can clearly understand the pros and cons of the two designs.

Software Testing Basics (iv) test types