assert_
glossary ↓ downloads
track: java · selenium
suite 07 · suite test

Suite test: Real-world engineering

6 questionsevery test must pass to merge

This is the suite's regression gate. Answer every question, then run the suite. Wrong answers show an explanation — read it, then re-run. In this course, like on a real team, you don't merge on a red build.

01.ConfigReader.get() checks System.getProperty(key, …) first so that…
That fallback line is how CI points one suite at dev, staging, or prod. Quietly the most professional line in the course.
02.With on: push in the workflow file, your tests run…
That's the whole point of CI: nobody has to remember. Add workflow_dispatch for a manual button and cron for nightly.
03.Tests pass locally but fail only in CI. The #1 suspect from this course:
Headless defaults to a small viewport; sites render mobile layouts and elements move. The lesson pre-solved this mystery for you.
04.The recommended junit-platform.properties parallel setup runs…
Classes share nothing; each test still gets its own browser from @BeforeEach. Method-level concurrency needs extra care.
05.On failure, the workflow uploads artifacts. Which ones, per this course?
The evidence pair: a picture of the moment of death plus the parsed test reports — enough to diagnose without re-running.
06.“Every decision lives in exactly one place” is the shared principle behind…
Locators in one class, URLs in one file, browser creation in one factory: a change is always a one-file fix.
passing marks this suite test complete on the roadmap · revision aid: the suite cheatsheet
← Headless & parallel — speed Capstone project →