|testing tools 125 questions (86-125)|
86) What is Negative Testing?
Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.
87) What is Path Testing?
Testing in which all paths in the program source code are tested at least once.
88) What is Performance Testing?
Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".
89) What is Positive Testing?
Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.
90) What is Quality Assurance?
All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.
91) What is Quality Audit? burberry outlet
A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.
92) What is Quality Circle?
A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.
93) What is Quality Control?
The operational techniques and the activities used to fulfill and verify requirements of quality.
94) What is Quality Management?
That aspect of the overall management function that determines and implements the quality policy.
95) What is Quality Policy?
The overall intentions and direction of an organization as regards quality as formally expressed by top management.
96) What is Quality System?
The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.
97) What is Race Condition?
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.
98) What is Ramp Testing?
Continuously raising an input signal until the system breaks down.
99) What is Recovery Testing?
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.
100) What is Regression Testing?
Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.
101) What is Release Candidate?
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).
102) What is Sanity Testing?
Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.
103) What is Scalability Testing?
Performance testing focused on ensuring the application under test gracefully handles increases in work load.
104) What is Security Testing?
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.
105) What is Smoke Testing?
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.
106) What is Soak Testing?
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.
107) What is Software Requirements Specification?
A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software
108) What is Static Analysis?
Analysis of a program carried out without executing the program.
109) What is Static Analyzer?
A tool that carries out static analysis.
110) What is Static Testing?
Analysis of a program carried out without executing the program.
111) What is Storage Testing?
Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.
112) What is Stress Testing?
Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.
113) What is Structural Testing?
Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing.
114) What is System Testing?
Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.
115) What is Thread Testing?
A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.
116) What is Top Down Testing?
An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.
117) What is Total Quality Management?
A company commitment to develop a process that achieves high quality product and customer satisfaction.
118) What is Traceability Matrix?
A document showing the relationship between Test Requirements and Test Cases.
119) What is Usability Testing?
Testing the ease with which users can learn and use a product.
120) What is Use Case?
The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.
121) What is Unit Testing?
Testing of individual software components.
122) What is Validation?
The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The techniques for validation is testing, inspection and reviewing
123) What is Verification?
The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.
124) What is Volume Testing?
Testing which confirms that any values that may become large over time (such as accumulated counts, logs, and data files), can be accommodated by the program and will not cause the program to stop working or degrade its operation in any manner.
125) What is Walkthrough?
A review of requirements, designs or code characterized by the author of the material under review guiding the progression of the review.