True
False
Programming standard violations
Referring a variable with an undefined value
Security vulnerabilities
All Above
End Usability License Agreement
End User License Agreement
End User License Arrangement
End User License Attachment
Alpha release
Beta release
Test release document
Build
Computer Aided Software Testing
Computer Aided Software Tools
Computer Analysis Software Techniques
None
True
False
Functional testing
Structural Testing
All of the above
None of the above
Gray Box Testing
Hybrid Testing
A. & B.
None
True
False
Incident management tools
Requirements management tools
Configuration management tools
None
True
False
True
False
Determine the productivity of programmers
Eliminate the need for future program maintenance
Eliminate every error prior to release
Uncover software errors
Incorrect program behaviour due to a fault in the program
Bug found before product Release
Bug found after product Release
Bug found during Design phase
When the code is complete.
When the design is complete.
When the software requirements have been approved.
When the first code module is ready for unit testing
This question is impossible to answer
This question is easy to answer
The answer depends on the risk for your industry, contract and special requirements
This answer depends on the maturity of your developers
Data tester
Boundary tester
Capture/Playback
Output comparator.
Statement Coverage
Pole Coverage
Condition Coverage
Path Coverage
Defects
Trends analysis
Test Effectiveness
Time Spent Testing
Error condition hiding another error condition
Creating a test case which does not reveal a fault
Masking a fault by developer
Masking a fault by a tester
Functionality
Usability
Supportability
Maintainability
Lack of technical documentation
Lack of test tools on the market for developers
Lack of training
Lack of Objectivity
Missing Statements
Unused Branches
Dead Code
Unused Statement
2
3
4
5
Stub
Driver
Proxy
None of the above
Quality is job one
Zero defects
Conformance to requirements
Work as designed
Is the same as equivalence partitioning tests
Test boundary conditions on, below and above the edges of input and output equivalence classes
Tests combinations of input circumstances
Is used in white box testing strategy
0,1900,2004,2005
1900, 2004
1899,1900,2004,2005
1899, 1900, 1901,2003,2004,2005
2 Test Cases
3 Test Cases
4 Test Cases
Not achievable
Statement and branch testing
Usability testing
Security testing
Performance testing
Takes minutes of the meeting
Mediates between people
Takes telephone calls
Writes the documents to be reviewed
Requirements
Design
Code
Decision table
System testing
Usability testing
Performance testing
Both B & C
Done by the Developer
Done by the Test Engineers
Done By Management
Done by an Entity Outside the Project’s sphere of influence
Defect prevention
Deliverable base-lining
Management reporting
None of the above
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
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
Execution
Design
Planning
Check Exit criteria completion
Does not meet people needs
Cultural difference
Loss of control over reallocation of resources
Relinquishments of control
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.