What is a test bed?
A test bed is a test environment used for testing an application. A test bed configuration can consist of the hardware and software requirement of the application under test including - operating system, hardware configurations, software configurations, tomcat, database etc.
What is defect density?
Defect density is the measure of density of the defects in the system. It can be calculated by dividing number of defect identified by the total number of line of code(or methods or classes) in the application or program.
Severity: It is the extent to which the defect can affect the software.
Priority: Priority defines the order in which we should resolve a defect. Should we fix it now, or can it wait?
Give an example of Low priority-Low severity, Low priority-High severity, High priority-Low severity, High priority-High severity defects.
- Low priority-Low severity - A spelling mistake in a page not frequently navigated by users.
- Low priority-High severity - Application crashing in some very corner case.
- High priority-Low severity - Slight change in logo color or spelling mistake in company name.
- High priority-High severity - Issue with login functionality.
What is a blocker?
A blocker is a bug of high priority and high severity. It prevents or blocks testing of some other major portion of the application as well.
What is stub?
In case of top-down integration testing, many times lower level modules are not developed while beginning testing/integration with top level modules. In those cases Stubs or dummy modules are used that simulate the working of modules by providing hardcoded or expected output based on the input values.
What is driver?
In case of bottom-up integration testing, drivers are used to simulate the working of top level modules in order to test the related modules lower in the hierarchy.
In case of bottom-up integration testing, drivers are used to simulate the working of top level modules in order to test the related modules lower in the hierarchy.
What is Difference between Ad-hoc and Monkey Testing?
Ad-hoc Testing is performed without any planning or preparation. After the program is functional, the programmer or tester will test the software using his knowledge of the program. Monkey Testing is similar to Ad hoc Testing. However, it can be done without any knowledge or information about the software.
What is the difference between regression and retesting?
Regression testing involves testing the application to verify that a new code change doesn't affect the other parts of the application. Whereas, in retesting, we verify if the fixed issue is resolved or not.
What is code coverage?
Code coverage is the measure of the amount of code covered by the test scripts. It gives the idea of the part of the application covered by the test suite.
Code coverage is the measure of the amount of code covered by the test scripts. It gives the idea of the part of the application covered by the test suite.
What is cyclomatic complexity?
Cyclomatic complexity is the measure of the number of independent paths in an application or program. This metric provides an indication of the amount of effort required to test complete functionality. It can be defined by the expression -
L – N + 2P, where:
L is the number of edges in the graph
N is the number of node
P is the number of disconnected parts
What is the difference between testing and debugging?
Testing is the primarily performed by testing team in order to find the defects in the system. Whereas, debugging is an activity performed by development team. In debugging the cause of defect is located and fixed. Thus removing the defect and preventing any future occurrence of the defect as well.
What is an exit criteria?
Exit criterion is used to determine whether a given test activity has been completed or NOT. Exit criteria can be defined for all of the test activities right from planning, specification and execution. Exit criterion should be part of test plan and decided in the planning stage.
What is Requirement Trace-ability Matrix(RTM)?
Requirement Traceability Matrix or RTM captures all requirements proposed by the client or development team and their traceability in a single document delivered at the conclusion of the life-cycle.
In other words, it is a document that maps and traces user requirement with test cases. The main purpose of Requirement Traceability Matrix is to see that all test cases are covered so that no functionality should miss while testing.
