.
Discussed informally with the developer
Ignored unless it happens several times
Formally logged for further investigation
Classified as a defect until proven otherwise
Testers
Developers
Users
All of the above
Inputs
The person who caused the incident The person who caused the incident - correct
Actual Results and expected results
Date and Time
A. Impact - the actual or potential damage that could be caused by the incident
B. Who performed the tests
Neither a nor b
Both a and b
The amount of time needed for testing decreases
Testers are friendlier with the developers
Testers are generally friendlier with the system's end users
None of the above
Less independent
More independent
None of the above
Equally independent
1, 2, and 5 are true; 3 and 4 are false
2, 3 and 4 are true; 1 and 5 are false
1, 2, and 4 are true; 3 and 5 are false
1, 2, and 3 are true; 4 and 5 are false
Recommend project actions
Execute tests
Estimate time and cost
Recommend project actions
Data for previous similar projects are not available
The development to test time ratio is unknown
Domain subject matter experts are not available to assist
Non-functional requirements often are not well documented
A document specifying the test conditions for a test item, establishing the detailed test approach and identifying the associated high level test cases
A document specifying a set of test cases ( objective, inputs, test actions, expected results and execution preconditions) for a test team
A document reporting on any event that occurred during testing which requires further investigation
A document describing the scope, approach, resources, and schedule of intended test activities
Risk-based test approach
Business risks of insufficient testing
Risks and contingencies
Has no section for risks
No medium or high severity defects remain uncorrected
All planned test coverage goals have been met
All planned test cases have been written, executed, and passed
All of the above
A group of people responsible for evaluating, approving or disapproving, and monitoring proposed changes items
A group of people responsible for preventing changes to items under configuration management control
A group of people who make approved changes to items under configuration management control
A visible board , posted in a public place, on which items under configuration management control are displayed and tracked
It is unclear why code changes were made
Regression testing is required
Modifications to documents or code are overwritten
It is unclear what version of the software is being tested
Test Plans
Test Environment
Test Scripts
All of the above
Approvals
List of all defects found
Variances from the test plans
Comprehensiveness assessments
Test Control
Test Leadership
Test monitoring
Test design
Component or system ordered from highest to lowest risk
Component or system per developer
Component or system divided by the size of the component or system
Component or System
Extend the schedule to allow more time to complete the planned tests
Automate some of the manual tests
Prioritize which tests to perform and which not to perform
Add additional testers who have experience on the system under test
Can improve the parameters it is measuring
Has no effect on the parameters it is measuring
Can adversely affect the parameters it is measuring
Does not integrate well into the development and / or testing process
Memory leaks
Ambiguous requirements statements
Designs that are too complex
Syntax errors in code
Files and databases in test results
Tests designed and tests executed
Coverage planned and coverage achieved
Tests required and tests designed
Trace test cases to requirements specifications
Code coverage
Interface to incident tracking tools
Support test planning and scheduling
Are generalized sets of multiple test cases
Rarely require revision by the tester
By-pass the user interface and interact with the test object directly
May be invalidated by small changes in the system
Represented in a table or spreadsheet describing actions
Scripts created automatically by capture/replay tools
Scripts created manually by testers
Represented in a table or spreadsheet containing decision tables Represented in a table or spreadsheet containing decision tables - correct
Wait!
Here's an interesting quiz for you.