Common knowledge of software testing

Acceptance testing is a stage of the system development lifecycle methodology. At this time, the relevant users and/or independent testers test and receive the system based on the test plan and results. It allows the System user to decide whether to receive the system. It is a test to determine whether the product meets the contractual or user-defined requirements. This is administrative and defensive control.

Ad hoc testing (random test), no written test cases, tests that record expected results, check lists, scripts or instructions. The function and performance of the software are checked based on the tester's experience. Random testing is an important supplementary means to execute test cases according to the test manual. It is an effective way and process to ensure the integrity of test coverage.

Alpha testing (alpha testing) is a test performed by a user in the development environment. It can also be a controlled test performed by the company's internal users in the simulated actual operating environment, alpha testing cannot be performed by programmers or testers.

Automated Testing uses automated testing tools for testing. Such tests generally do not require human intervention and are usually used in Gui, performance, and other tests.

Beta testing (beta testing) is a test performed by multiple users of the software in the actual use environment of one or more users. Developers are usually not present at the test site, and beta testing cannot be completed by programmers or testers.

Black box testing refers to a testing method in which testers do not care about how the program is implemented. Testing of Software defects based on software specifications by various input and observation of various output results of the software. Such testing does not consider the internal operating principles of the software, therefore, software is like a black box for users.

Bug (error), sometimes called defect (defect) or error, may cause unnecessary side effects due to programming errors in software programs, the functions and features of the software are inconsistent with the design specification or user requirements. Software defects are characterized by: the software does not meet the features specified in the product manual; the software has errors not indicated in the product manual; the software functions are beyond the scope specified in the product manual; software testers or users think that the software is hard to understand, difficult to use, and slow to run.

Bug report (Error Report), also known as "bug record (error record)", is a document that records the detected software error information, it usually includes error description, recurrence steps, captured error images, and comments.

Bug Tracking System (BTS), also known as "defect tracking system, DTS", is a dedicated database system for managing software test defects, it can efficiently complete software defect reporting, verification, modification, query, statistics, storage and other tasks. Especially suitable for testing and management of large-scale multilingual software.

Build (working version), incomplete software versions such as functions and performance used for internal testing during software development. The working version can be either an operable version of the system or a part of the system that shows some of the functions to be provided in the final product.

Compatibility testing, also known as "configuration testing", is used to test whether the software is compatible with other interaction elements of the system, for example: browser, operating system, hardware, etc. Verify the running status of the test object in different software and hardware configurations.

Capture/replay tool (capture/playback tool), a test tool that captures the input passed to the software during the test and can be later, repeat the execution process. This type of tool is usually used in Gui testing.

Crash (crash), a computer system or component suddenly and completely loses functionality, such as a sudden exit of a software or system or no response (crash ).

Debug, the developer determines the root cause of the error and the process of determining possible repair measures. Generally, when the subsystem or unit module code is complete, or an error is identified based on the test error report, the developer needs to execute the debugging process to solve the existing error.

Deployment (deployment), also known as shipment (release), refers to the phase in which the first version of the internal IT system passes a thorough test to form a product and deliver it to the paying customer.

Dynamic Testing (Dynamic Testing) is used to test the software by executing the software.

Exception (Exception/exception), an event that causes normal program execution to be suspended.

Functional testing (function testing), also known as behavioral testing (behavior testing), based on product features, operation descriptions and user solutions, test the features and operational behavior of a product to determine that they meet design requirements. A functional test of the localization software to verify that the application or website works properly for the target user. Use appropriate platforms, browsers, and test scripts to ensure that the target user experience is good enough, just as applications are specially developed for this market.

Garbage characters (garbled characters) are meaningless characters displayed on the program interface. For example, if the program does not support double-byte character sets, these characters cannot be correctly displayed.

GB 18030 testing (GB 18030 test), the software supports testing of the GB 18030 character set standard capability, including the degree of support for the input, output, display, and storage of GB 18030 characters.

Installing testing (installation test) ensures that the software can be installed under normal and abnormal conditions, such as initial installation, upgrade, complete or custom installation. Exceptions include insufficient disk space and permission for creating directories. Verify that the software runs properly immediately after installation. Installation testing includes testing the installation code and the installation manual. The installation manual provides how to install and the installation Code provides the basic data that can be run by installing some programs.

Integration Testing (integration test) is integrated by all components of the test system to identify the relations between the components of the tested system and errors in interfaces. This test is generally performed after the unit test.

International TESTING (International TESTING): The purpose of international testing is to test the software's international support capability, discover potential problems of software internationalization, and ensure that the software can run normally in different regions of the world. The internationalization test uses each possible international input type and checks whether the product functions are normal for any region or region. The emphasis of the Software Internationalization test is to execute the input/output functions of international strings. International Test Data must contain a mix of East Asian, German, complex script characters, and (optional) English characters.

Localizability testing (localization capability test). Localization capability refers to the ability to translate the user interface of a program into any target language without re-designing or modifying the code. To reduce the cost of localization capability testing and improve the testing efficiency, the localization capability side is usually carried out on the pseudo-localization version of the software. Typical errors found in the localization capability test include hard encoding of characters (that is, the characters to be localized in the software are written inside the Code), and the country-specific value is set for the characters to be localized, when the software is running, it locates at the control position. icons and bitmaps contain the text to be localized, and the user interface of the software is inconsistent with the terminology of the document.

Load Testing is used to test the system performance when resources are overloaded to detect design errors or verify the system's load capabilities. In such a test, the test object will assume different workloads to evaluate and evaluate the performance and behavior of the test object under different workload conditions and the ability to continue normal operation. The purpose of the load test is to determine and ensure that the system can still run normally when it exceeds the maximum expected workload. In addition, the load test also evaluates performance characteristics, such as response time, transaction processing rate, and other time-related aspects.

Localization testing (localization test), the object of the localization test is the localized version of the software. The purpose of the localization test is to test the Software Localization quality set for a specific target region. The environment for localization testing is to install localized software on a localized operating system. The test methods can be divided into basic function testing, installation/uninstall testing, and software and hardware compatibility testing in the local area. The test content mainly includes the interface layout after software localization and the language quality of software translation, including software, documentation and on-line help.

Performance testing: A test that evaluates whether a product or component meets the performance requirements. Includes load testing, strength testing, database capacity testing, benchmark testing, and other types.

Pilot testing (pilot testing), in software development, verifies the system's ability to handle typical operations based on real hardware and customers. In software outsourcing testing, pilot testing is usually a form of testing capability of the customer to check the software testing company, only through the customer-specific pilot testing, the software testing company can accept the software testing of the customer's real software project.

Portability testing, which is designed to prove that the software can be migrated to a specified hardware or software platform.
Priority (priority) refers to the importance of errors from a business perspective, especially from the perspective of customers and users. It refers to the impact of errors on the feasibility and acceptability of the system. Compare with "severity (severity.

Quality Assurance (Quality Assurance QA), all activities undertaken to ensure that the products delivered by a development organization meet performance requirements and established standards and processes.

Regression testing (regression test), retests the previous test after modification to ensure the correctness of the modification. In theory, regression tests are required for any new version of the software to verify that errors previously discovered and fixed are reproduced on the new software version.

Review: the process of submitting the product to project members, users, managers, or other related personnel for review or approval during product development.

Sanity testing, a simple test of the main functional components of the software to ensure that it can perform basic tests. Refer to "Smoke Testing (smoke test )".

Screen Shot (capture screen,). During software testing, all or part of errors (Windows, menus, and dialogs) on the software interface are stored as image files using dedicated tools, to facilitate subsequent processing.

Severity (severity), the extent to which errors affect the system to be tested, the likelihood of occurrence under the conditions of end users, and the extent to which software errors impede system use. Compared with "priority (priority.

Smoke Testing (smoke test): The smoke test object is the version of each newly compiled software that needs to be formally tested. The purpose is to confirm that the basic functions of the software are normal and subsequent formal tests can be conducted. The implementer of the smoke test is the version compiler. See sanity testing )".

Software life cycle begins with the conception of a software product and ends with the period during which the product is no longer used.

Static testing (Static Test) does not pass execution to test a system. Such as code check, document check and review.

Structured Query Language (structured query statement, SQL) is a language used to query and process data in a relational database.

TBD (to be determined, TBD To be determined) is an ongoing task that has not yet been finalized.

Test, the process of executing the software to verify that it meets the specified requirements and detect errors. Checks the differences between existing conditions and evaluates the characteristics of software items. An activity of the software engineering process that runs the software under predetermined conditions to determine whether the software meets the expected results.

Test case is a set of test inputs, execution conditions, and expected results developed for a specific purpose, the goal is to test a program path or verify whether a specific requirement is met.

Testing coverage refers to the extent to which the test system covers the tested system, the extent to which a given test or a group of tests process all specified test cases of a given system or component.

Testing environment (test environment), Environment for testing, including test platform, test infrastructure, test lab and other facilities.

Testing item, used as the working version of the test object.

Testing plan describes the scope, methods, resources, and progress of the testing activity to be performed. It identifies test items, tested features, test tasks, who executes tasks, and plans for conflicting risks.

Testing procedure (test process) refers to a series of detailed steps for setting and executing a given test case and evaluating the test results.

Testing script is generally a series of commands for a specific test. These commands can be executed by automated testing tools.

Testing suite (test package), a set of execution frameworks in test use; a method for organizing test cases. In the test package, test cases can be combined to create unique test conditions.

Unit testing (unit test) refers to the basic test of a piece of code. Its actual size is not fixed. It is usually a function or subroutine, which is generally executed by developers.

A User Interface (UI) is a hardware and/or software that allows users to interact with computers in a broad sense. In a narrow sense, it refers to the visible appearance of the software and its underlying interaction with the user (menu, dialog box, window and other controls ).

User Interface testing (User Interface Test) is used to test whether the style of the user interface meets the requirements of the customer, whether the text is correct, whether the page is beautiful, whether the text and image combinations are perfect, and whether the operations are friendly. The purpose of the UI test is to ensure that the user interface provides users with access or browsing functions through the function of the test object. Ensure that the user interface complies with company or industry standards. Including user-friendly, user-friendly, and easy-to-operate tests.

White box testing (white box test), based on the internal working principle of the software for testing, code-based testing, testers can judge the quality of software by reading program code or by using one-step debugging in development tools. Generally, black box testing is implemented by the Project Manager in programmer development.