21⟩ What is Bug?
A fault in a program which causes the program to perform in an unintended or unanticipated manner.
“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 fault in a program which causes the program to perform in an unintended or unanticipated manner.
A graphical representation of inputs and the associated outputs effects which can be used to design test cases.
A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.
Computer Aided Software Testing.
A test suite that exercises the full functionality of a product but does not test features in detail.
Testing in which all branches in the program source code are tested at least once.
BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001.
A minimal software item for which a separate specification is available.
Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.
The generation of source code.
A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.
A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards.
An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.
Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.
The process of finding and removing the causes of software failures.
Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.
A modeling notation that represents a functional decomposition of a system.
A database that contains definitions of all data items defined during analysis.
A measure of the logical complexity of an algorithm, used in white-box testing.
Testing of programs or procedures used to convert data from existing systems for use in replacement systems.