Project plan
Business plan
Support plan
None of the above
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
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
Operability
Observability
Simplicity
Robustness
10-20
40-50
70-80
5-10
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
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
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
To freeze requirements
To understand user needs
To define the scope of testing
All of the above
Simple Loops
Nested Loops
Concatenated Loops
All of the above
White box
Black box
Green box
Yellow box
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
Being diplomatic
Able to write software
Having good attention to detail
Able to be relied on
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
Interim Test report
Final test report
Project status report
Management report
Top-down integration
Bottom-up integration
None of the above
Module integration
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
To ensure that all of the small modules are tested adequately
To ensure that the system interfaces to other systems and networks
To specify which modules to combine when and how many at once
To ensure that the integration testing can be performed by a small team
To specify how the software should be divided into modules
S = 4, t = 3, u = 2 and 5, v = 1
S = 4 and 5, t = 3, u = 2, v = 1
S = 1 and 5, t = 3, u = 2, v = 4
S = 5, t = 4, u = 3, v = 1 and 2
S = 4 and 5, t = 1, u = 2, v = 3
1 test for statement coverage, 1 for branch coverage
1 test for statement coverage, 2 for branch coverage
1 test for statement coverage. 3 for branch coverage
2 tests for statement coverage, 2 for branch coverage
2 tests for statement coverage, 3 for branch coverage
To know when a specific test has finished its execution
To ensure that the test case specification is complete
To set the criteria used in generating test inputs
To know when test planning is complete
To plan when to stop testing
1 test for statement coverage, 3 for branch coverage
2 tests for statement coverage, 2 for branch coverage
2 tests for statement coverage. 3 for branch coverage
3 tests for statement coverage, 3 for branch coverage
3 tests for statement coverage, 2 for branch coverage
How to fix the fault
How to reproduce the fault
Test environment details
Severity, priority
The actual and expected outcomes
Test items (i.e. software versions)
What is not to be tested
Test environments
Quality plans
Schedules and deadlines
Test items
Test deliverables
Test tasks
Test environment
Test specification
Only important in system testing
Only used in component testing
Never specified in advance
Most useful when specified in advance
Derived from the code
SC = 1 and DC = 1
SC = 1 and DC = 2
SC = 1 and DC = 3
SC = 2 and DC = 2
SC = 2 and DC = 3
I, iii & iv are true. Ii & v are false
Iii is true, I, ii, iv & v are false
Iii & iv are true. i, ii & v are false
I, iii, iv & v are true, ii us false
I & iii are true, ii, iv & v are false
1 test for statement coverage, 3 for branch coverage
1 test for statement coverage, 2 for branch coverage
1 test for statement coverage, 1 for branch coverage
2 tests for statement coverage, 3 for branch coverage
2 tests for statement coverage, 2 for branch coverage
Attend a tool exhibition
Invite a vendor to give a demo
Analyse your needs and requirements
Find out what your budget would be for the tool
Search the internet
As the first approach to deriving test cases
After more formal techniques have been applied
By inexperienced testers
After the system has gone live
Only by end users
Iv is correct and i,ii,iii are incorrect.
I,ii,iii is correct and iv is incorrect
Ii is correct and i,ii,iii are incorrect
Iii and iv are correct and i,ii are incorrect
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.