Manual testing
is a step-by-step operation performed manually by a human, and then observes the results to determine whether they correspond to the expected results. It is the most primitive type of testing without using any automated tools when executing test cases.
Automated Testing
A process of converting human-driven testing behavior into machine execution;
essence: programming testing, that is, writing one program to test another.
Black box testing Black box testing
, also known as functional testing, is a test to check whether each function can be used normally. In the test, the program is regarded as a black box that cannot be opened. The program interface is tested without considering the internal structure and internal characteristics of the program. It only checks whether the program function is used normally according to the requirements and specifications. Is there a correct input and output
White box testing White box testing
Also known as "structural testing" and "logic-driven testing";
definition: The test object is regarded as a transparent box, which allows testers to use the internal logic structure and related information of the program to design or select tests Use cases to test all logical paths of the program.
Debug
is the process of debugging a program and troubleshooting.
Test plan Test plan
is the main way for software testers and product development teams to communicate and complete indicators.
Purpose: To define the scope, methodology, resources, and schedule of testing activities.
Test case
The core of the test work is a set of input and output standards during testing, and a specific comparison of software requirements.
Contents: use case number, use case name, test background, preconditions, priority, importance, test data, test steps, expected results, actual results, remarks.
Bug Vulnerability
Means "bug" or "bug".
But now, we think of it more as in the computer system or program, if there are some undiscovered defects or loopholes hidden in
it , or a hidden functional defect. The existence of defects will cause the software product to fail to meet the needs of users to some extent.
Test report Test report
refers to writing the test process and results into documents, analyzing the problems and defects found, providing a basis for correcting the existing quality problems of the software, and laying the foundation for software acceptance and delivery.
Testing environment Deployment Testing environment deployment
includes hardware environment and software environment.
The hardware environment refers to the environment composed of servers, clients, network connection devices, and auxiliary hardware devices such as printers/scanners necessary for the test; the
software environment refers to the environment composed of the operating system, database and other application software when the software under test is running.
Sprint iteration
makes some modifications on the basis of the original software, which is called version iteration
Version version
refers to the version of the software upgrade, such as 1.0, 2.0
Functional testing
is to verify each function of the product, and test item by item according to functional test cases to check whether the product meets the functions required by users. ,
User interface testing (UI testing)
tests whether the layout of the functional modules of the user interface is reasonable, whether the overall style is consistent, and whether the placement of each control conforms to the customer's usage habits. More importantly, it must be convenient to operate and easy to understand. , whether the text in the interface is correct, whether the naming is uniform, whether the page is beautiful, whether the combination of text and pictures is perfect, etc.
Exception testing Exception testing
detects the handling of abnormal situations by the system. Exception testing covers handling of hardware or software exceptions
Unit testing
is the verification of the smallest unit of software design (module). The goal is to ensure that the module is correctly coded. Using the process design description as a guide, important control paths are tested to find errors within the module, usually the case The following is a white box, static testing of code style and rules, program design and structure, business logic, etc., early detection and resolution of errors that are not easy to appear
Integration testing
is also called assembly testing or joint testing, that is, the program modules are assembled in a one-time or multiplication manner, and the system interface is tested for correctness. Integration testing is to assemble all modules into subsystems or systems according to design requirements (such as according to the structure diagram) on the basis of unit testing, and conduct integration testing.
System testing System testing
is the testing of the entire system, combining hardware, software, operation Personnel as a whole, check whether it does not conform to the system specification
UAT User Acceptance Testing
A software testing activity performed before a product is released after the software product has completed unit testing, integration testing, and system testing. It is the final stage of technical testing, also known as delivery testing. The purpose of acceptance testing is to ensure that the software is ready and ready for use by end users to perform the intended functions and tasks of the software.
International testing The process of
making a product or software universally adaptable to different international markets so that it can adapt to multiple languages and cultural conventions without redesign. The real internationalization is in the process of software design and document development, so that the function and code design of the product or software can deal with multiple languages and cultural customs, and have good localization ability.
Performance testing refers to testing various performance indicators of the system by simulating a variety of normal, peak and abnormal load
conditions through automated testing tools, including the following types:
Check the operating status of the system and record the relevant data as a basic reference
(2) Load test: refers to continuously increasing the pressure on the system or increasing the duration of a certain pressure until one or more performance indicators of the system reach the safety critical value , such as a certain resource has reached a saturation state, etc.
(3) Stress test: Stress test is to evaluate the operation of the system when the system is under or exceeding the expected load, focusing on the processing capacity of the system under peak load or exceeding the maximum load.
(4) Stability test: In the case of loading a certain business pressure on the system, run the system for a period of time to check whether the system is stable.
(5) Concurrency test: test whether there are deadlocks or other performance problems when multiple users access the same application, the same module or data record at the same time
Priority Priority
Indicates the order of processing and correction of software defects, that is, which defects need to be fixed first, and which defects can be fixed later.
Severity Severity
refers to the degree of impact of the error on the system under test, the probability of occurrence under end-user conditions, the degree to which the software error hinders the use of the system
Quality assurance Quality assurance is to
ensure the quality activities of the whole life cycle of software products from birth to death, that is, all planned and systematic management activities to determine, achieve and maintain the required software quality
Smoking test
is to test the basic functions of the software. The purpose is to confirm that the basic functions of the software are normal, to ensure that the software system can run normally, and the follow-up normal test work can be carried out.
Software life cycle Software life cycle
The entire process from the creation of software until it is scrapped.
Static testing Static testing
The process of statically checking program code, interface, or documentation for possible errors without actually running the software under test.
Dynamic testing
The process of actually running the program under test, inputting the corresponding test data, and checking whether the actual output result matches the expected result
Structured query language The core language of the structured query language (SQL language)
database is a database query and programming language used to access data and query, update and manage relational database systems
Module Module
refers to a functional area or a piece of functional area that is complete and can be independent.
Test Scenario
refers to the user's point of view to identify real-world scenarios and application cases in use
Check Point Checkpoint
is a database event, and its fundamental purpose is to reduce crash recovery (Crash Recovery) time.
Testing coverage Test coverage
The scope of the test, that is, what needs to be tested and what is not tested, and from what perspective
Review
A means of evaluating the status of a software element or project to determine whether it is consistent with planned results and for improvement.
Screen shot
In software testing, all or part of the errors in the software interface are stored as image files using special tools for subsequent processing
TBD Pending Confirmation
is a work in progress not yet finalized in the test documentation
TBC pending
work pending
references:
This time there are too many references, here are the ones that helped me the most
without
Remark:
If there is any infringement, please contact by email, I am sorry.
This is only for learning personal notes, and if there is any reprint, please indicate the source.
Contact Email: [email protected]
Learn to test the penguin group together (chat, water group, do not disturb advertising): 826471103