Ruankao Software Evaluator (Intermediate) study materials
Ruankao Software Evaluator (Intermediate) study resources

Ruankao Software Evaluator (Intermediate) study plan

Ruankao Software Evaluator (Intermediate) · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Test Techniques and Test Case Design & Software Testing Fundamentals and Process Models

  • Explain the difference between black-box and white-box testing and list at least three techniques for each.

  • Apply equivalence partitioning and boundary value analysis to a given specification and derive test cases.

  • Draw a cause-effect graph for a simple function and convert it into a decision table.

  • Describe the fundamental test process (planning, monitoring, analysis, design, implementation, execution, evaluation, closure) and its outputs.

Your checkpoint

A test case design document for a login module using equivalence partitioning, boundary value analysis, and decision tables, with at least 12 test cases and expected results.

Week 2

Test Techniques and Test Case Design & Software Testing Fundamentals and Process Models

  • Construct a state transition diagram and derive test cases to achieve state transition coverage.

  • Apply statement and branch coverage to a given code snippet and calculate the percentage achieved by a set of test cases.

  • Compare verification and validation and explain how they map to the V-model.

  • List the entry and exit criteria for each test level in the V-model.

Your checkpoint

A coverage analysis report for a 30-line code sample showing statement and branch coverage for a designed test set, with at least 90% branch coverage and a justification of any uncovered branches.

Week 3

Computer Fundamentals and Software Engineering & Test Levels and Test Types

  • Describe the software development life cycle models (waterfall, V-model, iterative, agile) and their implications for testing.

  • Explain the purpose and content of a test plan according to IEEE 829 or ISO/IEC/IEEE 29119-3.

  • Differentiate unit, integration, system, and acceptance testing in terms of objectives, participants, and exit criteria.

  • Identify at least four types of functional and non-functional testing and give an example of when each is appropriate.

Your checkpoint

A one-page test plan for a small e-commerce checkout feature covering scope, approach, resources, schedule, and risk, aligned with a chosen life cycle model.

Week 4

Test Management and Defect Management & Software Testing Fundamentals and Process Models

  • Write a defect report with all essential fields (ID, summary, steps to reproduce, expected vs actual, severity, priority, environment).

  • Classify defects by severity and priority and justify the classification for three sample defects.

  • Describe the defect life cycle and the roles of tester, developer, and manager in each state.

  • Explain how to perform root cause analysis using the 5 Whys or fishbone diagram.

Your checkpoint

A defect report for a real or simulated bug, including a root cause analysis and a proposed process improvement to prevent recurrence.

Week 5

Test Automation, Tools and Environments & Performance, Load and Stress Testing

  • Compare at least three test automation tools (e.g., Selenium, JUnit, JMeter) and select one for a given scenario with justification.

  • Describe the test automation pyramid and explain the trade-offs between unit, service, and UI automation.

  • Design a load test scenario for a web application, specifying virtual users, ramp-up, duration, and metrics to collect.

  • Interpret performance test results (response time, throughput, error rate) and identify bottlenecks.

Your checkpoint

A performance test plan and a sample JMeter test script (or equivalent) for a simple API, with a results summary analyzing response times under 50 concurrent users.

Week 6

Performance, Load and Stress Testing & Security and Reliability Testing

  • Explain the differences between load, stress, spike, and endurance testing and when to use each.

  • Identify common security vulnerabilities (e.g., SQL injection, XSS, broken authentication) and describe how to test for them.

  • Describe reliability testing concepts: MTBF, MTTF, availability, and how to design reliability test cases.

  • Outline the OWASP Top 10 and select three relevant items to test for a web application.

Your checkpoint

A security and reliability test checklist for a web application covering at least 10 test items, each with a brief test approach and expected result.

Week 7

Software Quality and Standards & Computer Fundamentals and Software Engineering

  • Summarize the purpose and key requirements of ISO/IEC 25010 (SQuaRE) quality model.

  • Explain the difference between software quality assurance and software quality control.

  • Describe at least three software quality metrics (e.g., defect density, test coverage, mean time to failure) and how to use them.

  • Outline the CMMI levels and their relevance to test process improvement.

Your checkpoint

A quality assessment report for a hypothetical project that maps its test process to ISO/IEC 25010 characteristics and proposes two improvements based on CMMI.

Week 8

Professional English for Software Testing & Test Management and Defect Management

  • Read and interpret a software testing standard or article in English and summarize its key points.

  • Define at least 20 English software testing terms and use them in sentences.

  • Review all domains using practice questions and achieve at least 80% correct.

  • Create a personal exam-day strategy including time allocation and question triage.

Your checkpoint

A glossary of 20 English testing terms with Chinese translations and example sentences, plus a scored practice test result of at least 80%.

Milestones

Week 2: Can design test cases using at least four black-box and two white-box techniques and calculate coverage for a given code snippet.

Week 4: Can write a complete test plan and a defect report that meets industry standards, and explain the defect life cycle.

Week 6: Can design and interpret a performance test and list at least five security test cases for a web application.

Week 8: Achieve at least 80% on a full-length practice exam covering all domains, with no domain below 60%.