This quiz will helpful for istqb.
Checking that we are building the right system
Checking that we are building the system right
Performed by an independent test team
Making sure that it is what the user really wants
Will always be automated
Will help ensure unchanged areas of the software have not been affected
Will help ensure changed areas of the software have not been affected
Can only be run during user acceptance testing
We cannot run the test
It may be difficult to repeat the test
It may be difficult to determine if the test has passed or failed
We cannot automate the user inputs
2 is a valid reason; 1,3,4 & 5 are not
1,2,3,4 are valid reasons; 5 is not
1,2,3 are valid reasons; 4 & 5 are not
All of them are valid reasons for failure
You shorten the time required for testing
You do the best testing in the time available
You do more effective testing
You find more faults
Error guessing
Walkthrough
Data flow analysis
Inspections
Component testing should be performed by development
Component testing is also know as isolation or module testing
Component testing should have completion criteria planned
Component testing does not involve regression testing
Execution
Design
Planning
Check Exit criteria completion
Being diplomatic
Able to write software
Having good attention to detail
Able to be relied on
To freeze requirements
To understand user needs
To define the scope of testing
All of the above
Top-down integration
Bottom-up integration
None of the above
Module integration
Project plan
Business plan
Support plan
None of the above
Interim Test report
Final test report
Project status report
Management report
Defect prevention
Deliverable base-lining
Management reporting
None of the above
Does not meet people needs
Cultural difference
Loss of control over reallocation of resources
Relinquishments of control
10-20
40-50
70-80
5-10
Is unlikely to be completed on schedule
Is unlikely to cause a failure
Is likely to be fault-free
Is likely to be liked by the users
This question is impossible to answer
The answer depends on the risks for your industry, contract and special requirements
The answer depends on the maturity of your developers
The answer should be standardized for the software development industry
Operability
Observability
Simplicity
Robustness
White box
Black box
Green box
Yellow box
Simple Loops
Nested Loops
Concatenated Loops
All of the above
Stub
Driver
Proxy
None of the above
A black box testing technique used only by developers
A black box testing technique than can only be used during system testing
A black box testing technique appropriate to all levels of testing
A white box testing technique appropriate for component testing
A small team to establish the best way to use the tool
Everyone who may eventually have some use for the tool
The independent testing team
The vendor contractor to write the initial scripts
Variables not defined in the code
Spelling and grammar faults in the documents
Requirements that have been omitted from the design documents
How much of the code has been covered