STELA Advanced QA develops the skills needed to maintain and operate a test suite as the application changes. Move beyond individual tests to make coverage decisions, preserve meaningful checks, investigate failures, and deliver results another person can assess. The course builds on practical STELA QA Fundamentals competencies and uses the familiar STELA STORE environment. Start by selecting a justified set of cases and identifying the risks that remain outside your coverage. Maintain object recognition with Robot Maker and Computer Vision while preserving the business rules your tests must verify. Investigate changing interfaces, delayed responses, and intermittent failures without hiding unsuccessful attempts or weakening an expectation to obtain a pass. Strengthen your checks through complete catalog comparisons, a cart containing several products, independent calculations, and spreadsheet evidence reopened from disk. You will demonstrate that the suite detects a defect and distinguish functional failure, technical failure, and timeout. In a prepared integration environment, launch executions, connect reports to the correct run, and retrieve the evidence needed for a decision. The final project requires a maintained suite, a reproducible evidence package, and a handover another person can follow. You will also recover a compatible earlier version and explain your response to a new variant. No programming is required. Practical work uses the assigned lab and an existing pipeline configured for the course.

– Getting started: demonstrate the Fundamentals entry competencies and prepare your work log and evidence templates.
– Risk-based strategy and coverage: justify case selection, connect risks to evidence, and communicate residual risk.
– Maintainable design: preserve object identity and business checks through changes, and prepare a reproducible handover.
– Synchronization and intermittent failures: define completion conditions, investigate delays, and preserve attempt history.
– Quality of checks: compare complete lists and cart totals, verify persisted evidence, and demonstrate defect detection.
– Execution and communication: operate a prepared pipeline, identify each execution, retrieve evidence, and report outcomes accurately.
– Final project: deliver a maintained suite, support independent execution, recover an earlier version, and explain a new variant.