Quiz based on key concepts for the CTAL TM exam. 40 questions taken from a sample bank larger than 40 with 1 hour time limit. Questions and answers are randomized.
A requirements review meeting
A business analyst eliciting requirements
A database administrator designing a table
A test results report showing requirements coverage
Design tests from the requirements specification
Analyze design-related risks
Execute unit test cases
Write the test summary report
Design tests from the design specification
Component testing for each system
Component integration testing for each system
System testing for each system
Contract acceptance testing for each system
System integration testing
Test traceability
ISO 61508
Usability testing
Employee evaluations
The bug trend chart will reveal test progress problems while the test case trend chart will not.
The bug trend chart will show test coverage while the test case trend chart will not.
The test case trend chart will reveal test progress problems while the bug trend chart will not.
The test case trend chart will show test coverage while the bug trend chart will not.
Average days from defect discovery to resolution
Lines of code written per developer per day
Percentage of test effort spent on regression testing
Percentage of requirements coverage
The test plan should include risk analysis early in the process.
The test plan should list the requirements specification as an input to the risk analysis.
The test plan should assign specific bugs to specific developers.
The test plan should discuss the integration of reactive test techniques into test execution.
The test plan should specify overall project team metrics used to determine bonuses
Test plan
Test design specification
Incident report
Project plan
Their domain knowledge
Their technical expertise
Their testing expertise
Their management expertise
Impose retroactive financial penalties on this vendor for the number of bugs delivered on this project.
Perform an acceptance test for all systems received, with particular rigor for this vendor.
Cancel the contract with this vendor and put it on an industry blacklist.
Require the vendor's developers to attend training to improve their ability to write quality code.
Testing for performance problems
Hiring a contractor after a key test analyst quits
Procuring extra test environments in case one fails during testing
Performing a project retrospective using test results
Requirements are complete and furnished early
Preventive in nature
Defect detection starts late
Manage requirements
Requirements are not complete
Not preventive in nature
Defect detection starts early
Identify and prioritize key quality risk areas
Requirements are complete and furnished early
Preventive in nature
Defect detection starts late
Manage requirements
Requirements are not complete
Not preventive in nature
Defect detection starts early
Identify and prioritize key quality risk areas
Schedule compression pressure is always there
Pressurized development
Experimental model of early testing and not confidence building
Test team involved late
Schedule compression pressure is always there
Regression of N+1 increment is always complex
Bugs planning failure
Lack of testing culture in agile world
Schedule compression pressure is always there
Flexibility in TC and design changes of system is too often
Experimental model of early testing and not confidence building
Dealing with unknowns
Creates uncertainty in relating other test work products (e.g., test cases) to the test basis and test objectives, thus providing better and more detailed monitoring and control for a Test Manager.
Contributes to defect injection, as discussed in the Foundation Level, by occurring early in a project for higher levels of testing, as soon as the test basis is established and potentially before system architecture and detailed design are available.
Potentially will influence and direct not just other testing activities, but also other development activities.
Level of formality needs to be defined and implemented across the team.
Lightweight test design documentation methods, such as checklists, are being used due to accommodate the development lifecycle, cost and/or time constraints or other factors.
Little or no formal requirements or other development work products are available as the test basis
The project is large-scale, complex or high risk and requires a level of monitoring and control that cannot be delivered by simply relating test cases to development work products.
Less complex projects where simple hierarchical relationships exist between what is to be tested and how it is to be tested.
The activity that defines “how” something is to be tested.
The activity during which tests are organized and prioritized by the Test Analysts.
Traceability from the test results back to the test conditions, the test basis, and ultimately the test objectives, and also from the test objectives forward to the test results.
The information requirements and methods for collection and are part of test planning, monitoring and control.
Test completion check
Test artifacts handover
Lessons learned
Archiving results
Test case design
Risk assessment
Identification of test cases that relate to user requirements
Development of the formal test plan
All of the work products and activities for a given phase (e.g., requirements, design, implementation, unit testing, integration testing, system testing, and acceptance testing) are completed before the next phase begins.
The features to be implemented are grouped together (e.g., according to business priority or risk), and then the various project phases, including their work products and activities, occur for each group of features.
Work products and activities for each iteration are concluded before the next iteration starts.
Prototypes are used early in the project to confirm feasibility and to experiment with design and implementation decisions, using the level of business priority and technical risk to select the order in which the prototyping experiments are carried out.
Prototypes are used early in the project to confirm feasibility and to experiment with design and implementation decisions, using the level of business priority and technical risk to select the order in which the prototyping experiments are carried out.
Work products and activities for each iteration are concluded before the next iteration starts.
The features to be implemented are grouped together (e.g., according to business priority or risk), and then the various project phases, including their work products and activities, occur for each group of features.
All of the work products and activities for a given phase (e.g., requirements, design, implementation, unit testing, integration testing, system testing, and acceptance testing) are completed before the next phase begins.
The features to be implemented are grouped together (e.g., according to business priority or risk), and then the various project phases, including their work products and activities, occur for each group of features.
All of the work products and activities for a given phase (e.g., requirements, design, implementation, unit testing, integration testing, system testing, and acceptance testing) are completed before the next phase begins.
Work products and activities for each iteration are concluded before the next iteration starts.
Prototypes are used early in the project to confirm feasibility and to experiment with design and implementation decisions, using the level of business priority and technical risk to select the order in which the prototyping experiments are carried out.
Involves comparing actual progress against the plan and implementing corrective actions when needed.
Can be identified by analysis of the test basis, test objectives, and product risks.
Involves the identification of test cases by the stepwise elaboration of the identified test conditions or test basis using test techniques identified in the test strategy or the test plan.
Is the activity in which test designs are implemented as concrete test cases, test procedures, and test data.
Test planning starts at the initiation of the test process for that level and continues throughout the project until the completion of closure activities for that level.
Negotiation should include consultation with relevant project stakeholders about the schedule.
Members of the test team provide information required for exit criteria reporting to avoid having to conduct a lessons learned meeting after testing is completed.
Ensure that effective processes are in place to provide project status reports for users.
Wait!
Here's an interesting quiz for you.