Ruankao Software Evaluator (Intermediate)

A written exam with two components: multiple-choice questions covering all ten syllabus domains, and case study or short-answer questions where you analyse a scenario and produce test designs, coverage analysis or defect reports. Both are paper-based in most sittings. Confirm the current arrangement, including whether the sections are sat together, on the official site.

Harder than tool-vendor certificates because it tests reasoning, not recall. The multiple-choice part is passable with syllabus study, but the case study section separates candidates: you must choose appropriate techniques, justify coverage, and write cases another engineer could execute. Candidates with real project experience usually find the case section far more tractable.

Most working testers need a few months of part-time study. Start with test techniques and case design, since they carry weight and feed the case section. Then cover testing fundamentals and process models, test levels and types, and management. Leave performance, security and standards later, and revise professional English vocabulary throughout rather than cramming it.

Test techniques and case design, testing fundamentals and process models, and test levels and types together form the largest share of the syllabus. Master structural coverage criteria (statement, decision, condition, path) and specification-based techniques cold. Performance and security testing appear in smaller proportion but often surface in case questions, so know the standard workflow and metrics for each.

Retake rules, waiting periods and any limits on attempts are set by the administering body and can change between sittings. The exam is generally offered on a fixed annual schedule, so plan around the published dates. Check the official site for the current retake policy and registration windows rather than relying on second-hand accounts.

Each component is scored separately and both must reach the required threshold; a strong multiple-choice score will not compensate for a weak case study paper. The passing score is set and published by the issuing authority and is not fixed permanently. Verify the current thresholds and result-release dates on the official site.

Three recurring reasons: writing vague cases with no concrete input data or expected result; applying a technique without explaining why it fits the scenario; and running out of time because they over-answer the first question. Practise full papers under timed conditions and rehearse concise, tabular answers that state inputs, steps and expected outputs explicitly.

Not strictly, but it helps. Automation, tools and environments is a syllabus domain, and case questions may ask you to select tools, design a test framework or judge when automation is worthwhile. Familiarity with a scripting language and a common test tool makes those questions much easier and improves your credibility in interviews afterwards.

Use them for diagnosis, not memorisation. Sit one cold to identify weak domains, then study those areas before attempting another. For case questions, write full answers before reading any model answer, and compare structure rather than wording. Note recurring scenario types - coverage analysis, defect triage, performance test design - and build a reusable answering template for each.

Only on the official website of the administering authority for the computer技术与软件专业技术资格考试. Third-party sites often carry outdated schedules and fees. The official body publishes the current examination calendar, registration procedure, fee schedule and scoring rules; treat any figure you see elsewhere as unverified until you have checked it there.