81⟩ What is Software Testing?
A set of activities conducted with the intent of finding errors in software.
“QA Testing Interview Questions and Answers will guide us now that Software QA Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software QA Testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Learn QA Testing by this Software QA Testing Interview Questions with Answers guide”
A set of activities conducted with the intent of finding errors in software.
A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software/
Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.
A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.
Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.
Performance testing focused on ensuring the application under test gracefully handles increases in work load.
Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.
A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).
Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.
Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.
Continuously raising an input signal until the system breaks down.
A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.
A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.
A program or test tool used to execute a tests. Also known as a Test Driver.
Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.
The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.
A program or test tool used to execute a tests. Also known as a Test Harness.
Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc. A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. Test Driven Development? Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.
An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.
The process of exercising software to verify that it satisfies specified requirements and to detect errors. The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829). The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component. What is Test Automation? It is the same as Automated Testing.