NCT Tester Competence Assessment study plan
NCT Tester Competence Assessment · Give each week a clear focus.
8 weeks · About 7 hours per week
Test Design Techniques (Black-Box and White-Box) & Software Testing Fundamentals and Terminology
Define and distinguish black-box and white-box techniques, then classify all technique names in Domain 4 by category
Apply equivalence partitioning and boundary value analysis to three separate input specifications, deriving partitions and boundaries from scratch
Write a set of test cases from an equivalence-partition and boundary-value analysis of a numeric input field with documented valid and invalid partitions
Explain the seven ISTQB-style testing principles in your own words and match each to a concrete example from your own work
Your checkpoint
A one-page technique cheat sheet plus 15 derived test cases (with partitions and boundaries annotated) for a single input specification
Test Design Techniques (Black-Box and White-Box)
Construct decision tables for two business-rule scenarios with combined conditions and verify the resulting rule count
Apply state transition testing to a documented workflow, drawing the state diagram and deriving valid and invalid transition cases
Apply pairwise and classification-tree thinking to a multi-parameter configuration and justify the coverage reduction
Compute statement and decision coverage for a small code fragment by hand and identify which branches remain uncovered
Your checkpoint
A portfolio of four worked exercises (decision table, state diagram with cases, pairwise combination set, and a hand-calculated coverage table) each with a short rationale for technique selection
Test Levels, Test Types, and the Software Development Lifecycle & Software Testing Fundamentals and Terminology
Map the test levels (component, integration, system, acceptance) to their typical objectives, entry criteria, and responsible roles
Differentiate functional from non-functional test types and give two realistic examples of each in a project context
Describe how each test level fits into a sequential, iterative, and incremental lifecycle model
Explain the tester's role in agile ceremonies and how shift-left changes test activities
Use correct terminology (verification, validation, error, defect, failure, test basis) in written explanations without mixing them up
Your checkpoint
A lifecycle matrix table mapping each test level to objectives, test basis, typical defects found, and lifecycle-model variations
Static Testing and Review Techniques
Describe the formal review process stages and the responsibilities of each named role
Distinguish the review types by formality, and select the appropriate type for three given work products
Apply a checklist-based review to a supplied requirements paragraph and log findings classified by type and severity
Explain the value and limits of static analysis and identify defect classes it typically detects
Your checkpoint
A review report on a one-page requirements excerpt containing at least eight logged findings with classification, severity, and a recommendation per finding
Test Planning, Estimation, and Monitoring
Draft a test plan outline covering scope, approach, entry and exit criteria, and risks, aligned to a stated test strategy
Apply at least two estimation approaches (for example metric-based and expert-based) to the same scope and reconcile the differences
Define monitoring metrics (such as defect detection percentage, test execution progress, and coverage) and explain what each reveals
Write meaningful entry and exit criteria for a release and justify each criterion
Your checkpoint
A complete test plan for a hypothetical release plus an estimation worksheet showing two methods and a reconciliation note
Defect Management and Risk-Based Testing & Test Planning, Estimation, and Monitoring
Write a defect report with all essential fields and a reproducible summary for a described failure
Classify defects by severity and priority and justify cases where the two diverge
Perform a risk assessment using likelihood and impact, ranking at least six product risks and assigning test effort accordingly
Explain how risk level influences test depth, technique choice, and prioritization of test execution
Describe how defect metrics feed back into test monitoring and control decisions
Your checkpoint
A risk register of at least six ranked product risks with a matching test-approach column, plus three fully written defect reports
Test Tools, Automation, and Test Environment Management
Categorize test tools by the activity they support and state the benefits and risks of each category
Explain the purpose and risks of test automation, including what should and should not be automated
Describe the components of a test environment and the considerations for provisioning, configuration, and data management
Outline a pilot project for introducing a tool, including evaluation criteria and success measures
Your checkpoint
A tool evaluation and environment plan covering at least five tool categories, an automation suitability assessment, and an environment checklist
Professional Conduct and Communication & Software Testing Fundamentals and Terminology & Test Design Techniques (Black-Box and White-Box)
Apply communication principles to draft a concise status report and an escalation message for a missed exit criterion
Explain the tester's professional and ethical responsibilities, including independence and handling conflicting stakeholder pressure
Complete a timed mixed-topic practice set weighted by domain percentage and review every incorrect answer to its root cause
Re-derive the highest-weight technique examples from memory to confirm retention
Your checkpoint
A timed practice-set score log with root-cause notes for each error plus two written communications (status report and escalation message)
Milestones
Week 2: Can derive equivalence partitions, boundaries, a decision table, and a state transition set for an unfamiliar specification without notes, and can hand-calculate decision coverage correctly
Week 4: Can explain every review role and review type from memory, and produce a classified finding log from an unseen work product
Week 6: Can write a complete defect report and a ranked risk register for an unfamiliar scenario, and justify severity-versus-priority divergences
Week 8: Scores at or above 75 percent on a timed mixed-topic practice set weighted by domain percentage, with all errors traced to a root cause