Tester's dictionary [A-H] | Software testing terms as used inside the Industry

Emulator 

An emulator is a program that pretends to be another specific device or program that other components expect to interact with. 

End to End Testing 

End-to-end testing is a technique used to test whether the flow of an application is performing as designed from start to finish. The purpose of carrying out end-to-end tests is to identify system dependencies and to ensure that the right information is passed between various system components and systems. 

Endurance Testing 

Endurance testing involves testing a system with a significant load extended over a significant period of time, to discover how the system behaves under sustained use. Example: in software testing, a system may behave exactly as expected when tested for 1 hour but when the same system is tested for 3 hours, problems such as memory leaks cause the system to fail. 

Entry Criteria 

Entry criteria are the minimum set of constraints that should be met in order to start the testing work. Entry criteria are documented and signed off during the test planning phase and is included in the test plans.

Equivalence Partitioning Testing 

Equivalence partitioning is a Test Case Design Technique to divide the input data of software into different equivalence data classes. Test cases are designed for equivalence data class. This method reduces the time necessary for testing software using less and effective test cases. 

Error 

It is due to human actions like code is not following the standard, if there is some mistake in syntax or might be there are some mistakes in which database connectivity code. 

Error Guessing 

It is a method on guessing the error which can prevail in the code. It is basically an experience based technique where the test analyst uses their experience to guess the erroneous areas of the application. 

Error Seeding 

Error Seeding is the process of adding known faults intentionally in a program for the reason of monitoring the rate of detection & removal and also to estimate the number of faults remaining in the program.

Exhaustive Testing 

Exhaustive Testing, as the name suggests is exhaustive. In this type of testing we try to check the output given by the software by entering all the possible combination of inputs, in fact we use all the permutations and combinations of the inputs. Each element of code is verified under this process. 

Exit Criteria 

Exit Criteria make sure that whether testing is completed and the application is ready for release.

• Metrics
• Test Summary Report
• Defect Analysis Report 

Expected Outcome 

Expected output is actual output after execution of the test case.

Exploratory Testing 

Exploratory testing is a way to testing that emphasizes the freedom and responsibility of each tester to continually optimize the value of his work by treating learning, test design, and test execution as mutually supportive activities that run in parallel throughout the project.