ctal-tm Test Management v3.0 Practice Questions

System Testing focuses on functional requirements, while Component Testing focuses on non-functional requirements.

Test planning at the System Test level is more focused on business risks and end-to-end behavior, whereas at the Component Test level, it is more focused on technical risks and structural coverage.

Defect management is only performed at the System Test level.

Test automation is only applicable at the Component Test level.

Conducting individual expert interviews with each stakeholder separately.

Using a generic industry checklist for gaming software risks.

Facilitating a structured brainstorming session using a quality characteristic taxonomy (e.g., from ISO 25010) as prompts.

Analyzing defect reports from a previous, unrelated project.

The skill level of the developer who wrote the code.

The test technique used to detect the related defects.

The combination of the likelihood of the risk occurring and the impact if it does occur.

The number of test cases planned to cover the risk.

Motivators, because their absence is causing satisfaction.

Motivators, because improving them will lead to high satisfaction.

Hygiene factors, because their absence is causing dissatisfaction.

Hygiene factors, because they are directly related to the challenging nature of the work.

Prioritizing rapid feedback on user interface changes over formal documentation.

Implementing a formal review process (e.g., inspection) for all test plans and test cases.

Creating and archiving detailed test logs as evidence of test execution for auditing purposes.

Conducting frequent, informal exploratory testing sessions.

Maintaining bidirectional traceability between requirements, test cases, and test results.

The seniority of the stakeholder who suggested the improvement.

The technical complexity of implementing the improvement action.

Alignment with the test team's preferred tools and technologies.

The expected return on investment (ROI) and alignment with project strategies.

Improve the quality of the payment processing module by finding as many defects as possible.

Execute 100% of all planned test cases for the user registration and login functionality by the end of the project.

Achieve 95% execution pass rate for all P1 and P2 priority test cases related to the checkout workflow within Sprint 4, with no outstanding critical defects.

Ensure the application performance is satisfactory for end-users before the final release date.

A reactive approach, focusing on exploratory testing sessions by domain experts to find usability issues late in the cycle.

A regression-averse approach, heavily automating all existing functional tests to ensure no new defects are introduced in core features.

An analytical, standards-based approach, integrating static analysis for security vulnerabilities in the code and dynamic accessibility testing using specialized tools and checklists.

A model-based approach, using state-transition diagrams to generate test cases that maximize functional path coverage of the citizen workflows.

Establishing strict entry/exit criteria for the migration test cycles based on data quality metrics, such as percentage of records successfully migrated and validated.

Defining a test approach that includes data validation tests at each stage of the ETL process, using reconciliation reports and data profiling tools.

Planning extensive usability testing sessions with end-users on the new CRM interface.

Organizing performance testing to ensure the new cloud CRM can handle peak user load.

Implementing a new defect management tool to better track UI-related bugs.

Implement a mandatory peer-review process for all new defect reports before they are assigned to developers.

Schedule more frequent defect triage meetings with the entire project team.

Increase the severity level of all defects to get faster attention from the development team.

Procure a new, more advanced defect management tool with more mandatory fields.