Configured checks for shared code

Computing · Software Engineering · ages 20-22

Name ______________________ Date ____________

A team's policy runs a build after each branch push, then tests. Merging requires both checks to pass and reviewer approval. What is the relative order of push, build, tests and an allowed merge?
- Push, tests, build, merge
- Push, build, merge, tests
- Push, build, tests, merge
A CI configuration enables a build job and automated tests on branch pushes. What does a triggered run check?
- Successful deployment to the production server
- Project preparation and the tested behaviour
- The branch's merge-conflict status
Passing a pipeline's configured checks automatically satisfies every completion and release requirement.
Circle one: True False
Checks start automatically after each push but report their final result only after 45 minutes. Which cost follows directly?
- A forty-five-minute pause between pushes
- A forty-five-minute wait for the final result
- A forty-five-minute loss of checks for changes pushed during the run
CI runs the expected setup, but code reads an untracked file present only on your laptop. What does the failure reveal?
- A dependency missing from the reproducible project setup
- A runner-permission problem with the file
- An assertion using an outdated expected file
A team's policy blocks merging while a required check fails. What is an appropriate next action?
- Accept the local pass and mark this check nonblocking
- Rerun the job until it passes, then merge without diagnosis
- Investigate the failure and restore a trustworthy required check
A developer dismisses a CI failure because the code passes locally. Which response is justified?
- Repair the runner to match the local setup
- Investigate the differing results without assuming the cause
- Revise the code to match the failing CI result
Both teams start checks on every push. A gets its final result after 7 minutes; B after 80. Which conclusion is justified?
- B waits longer for results; batching is a possible response
- B has less coverage because its checks take longer to finish
- B pushes less often to match the result schedule

Answer key

For grown-ups. Fold this page away before handing over the rest.

Configured checks for shared code W1-mt_z__G4nfjwh-s1

Push, build, tests, merge · The stated policy starts the build after a push, runs tests next, and permits merging only after passing checks and reviewer approval. Other CI configurations may use a different order.
Project preparation and the tested behaviour · The build checks project preparation, and tests check their specified observations. These jobs do not prove every execution correct.
False · A passing run satisfies its checks. Review, security or manual acceptance requirements may still remain.
A forty-five-minute wait for the final result · The final result is delayed by the stated duration. The prompt does not say checks stop running or pushes become impossible.
A dependency missing from the reproducible project setup · This case supplies the cause: the code relies on a local-only resource that the expected project setup does not provide.
Investigate the failure and restore a trustworthy required check · Investigate whether code, tests or runner setup caused the failure. Repair the cause rather than bypassing a valid required check.
Investigate the differing results without assuming the cause · The differing results are evidence to investigate. Neither a local pass nor a CI failure identifies the cause by itself.
B waits longer for results; batching is a possible response · B's final feedback takes longer. That can influence habits, but it does not determine batching or push frequency.