Static analysis tools are used only by developers
Compilers may offer some support for static analysis
Static analysis tools help find failures rather than defects
Interoperability (compatibility) testing, reliability testing, performance testing
System testing, performance testing
Load testing, stress testing, component testing, portability testing
Testing various configurations, beta testing, load testing
Number of detected defects, testing cost;
Number of residual defects in the test object.
Percentage of completed tasks in the preparation of test environment; test cases prepared
Number of test cases run / not run; test cases passed / failed
The test object, the test material and the test environment
The problem reports and the test material
Only the test object. The test cases need to be adapted during agile testing
The test object and the test material
One
Indefinite
Two
Four
To specify when to stop the testing activity
To set the criteria used in generating test inputs
To ensure that the test case specification is complete
To know when a specific test has finished its execution
100% branch coverage
100% condition coverage and 100% statement coverage
Equivalence class and boundary value coverage
No other white box coverage criterion is guaranteed to be fulfilled 100%
(I) and (II) are correct
(I) through (IV) are correct
(III) through (V) are correct
(I), (II) and (IV) are correct
Not enough qualified testers to complete the planned tests
Software delivery is behind schedule
Threat to a patient’s life
3rd party supplier does not supply as stipulated
Static analysis tools produce statistics during program execution
Configuration management systems allow us to provide accurate defect statistics of different configurations
Stress testing tools examine the behavior of the test object at or beyond full load
Performance measurement tools can be used in all phases of software life-cycle
(I) through (III) are correct
All alternatives are correct
(II) and (V) are correct
(I), (III) and (V) are correct
Identification (Software and hardware) of the VCR
Actual result
History of the report
Ideas for the test case improvement
Testing management
Synonym of testing the quality of service
Triggered by modifications, migration or retirement of existing software
Testing the level of maintenance by the vendor
Because incremental integration has better early defects screening and isolation ability
Because "big bang" integration is suitable only for real time applications
Incremental integration is preferred over "Big Bang Integration" only for "bottom up" development model
Because incremental integration can compensate for weak and inadequate component testing
A software development model that illustrates how testing activities integrate with software development phases
A software life-cycle model that is not relevant for testing
The official software development and testing life-cycle model of ISTQB
A testing life cycle model including unit, integration, system and acceptance phases
The version number of the test object
Test data and used environment
Identification of the test case that failed
The location and instructions on how to correct the fault
Network
Operational Model
Boundary value analysis
Test Procedure Planning
Testing performed on a single stand – alone module or unit of code
Testing after changes have been made to ensure that no unwanted changes were introduced
Testing to ensure that the system meets the needs of the organization and end user.
Users test the application in the developers environment
System Testing
Integration testing
Component testing
Maintenance testing
True
False
Validation techniques
Verification techniques
Both of the above
None of the above
Another name for decision coverage
Another name for all-edges coverage
Another name for basic path coverage
All the above
Testing Planning
Test Control
Test analysis and design
Test implementation
System testing
Component Testing
Incremental Testing
Big bang testing
State transition Testing
Static Testing
Transition testing
Statement testing
Moderator
Author
Reviewer
Recorder
What is selected for testing
Objectives and results
Expected results
Targets and misses
Before Integration testing
After unit testing
After component testing
After system testing
Test Analysis
Test Design
Test Execution
Test Planning
Coordinate the test strategy and plan with project managers and others
Decide about the implementation of the test environment
Write test summary reports
Review and contribute to test plans
Decision coverage
Condition coverage
Statement coverage
Path Coverage
Formal Reviews
Peer Reviews
Semi Formal Reviews
All of the above
State Transition Testing
Random Testing
Syntax Testing
Penetration testing
Same as glass box testing
Same as clear box testing
Both A. and B.
None of the above.
Reviewing and Inspecting
Inspecting and Testing
Reviewing and Testing
Reviewing, Inspecting and Testing.
Ensure that test cases test each input and output equivalence class at least once
Identify all inputs and all outputs
Identify equivalence classes for each input
All of the above
Same as static testing
Done by the developers
Both A. and B
None of the above
Person days
Person hours
Calendar months
None of the above
Unit testing
Algorithm specific testing
Compatibility testing
Black box testing
To identify problems with design
To solve the problems with design
Both A. and B
None of the above.
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.