Challenge 3: Explain Newman's Role in CI — Possible Solution
====================================================================

Running newman run collection.json in a CI pipeline actually verifies
that every request in the collection AND every pm.test() assertion
attached to those requests still behaves as expected — not just that
the API responds at all, but that its actual responses (status codes,
specific field values, chained variables extracted correctly) still
match what the test scripts assert. This catches real regressions: if
a backend change accidentally altered a response's shape or broke
login, the exact same test scripts written and verified manually in
Postman (Chapters 2-4) now catch that automatically on every commit,
with no human re-running anything by hand.

A NON-ZERO EXIT CODE should cause the pipeline to FAIL THE BUILD —
exactly the same principle pipelines1-4 established for any test step
in CI: a test failure must stop the pipeline (blocking a merge, or at
minimum flagging it clearly), not be silently ignored. If the pipeline
kept going and reported success anyway, the entire value of running
Newman in CI would be lost — broken API behavior could reach
production with a fully green pipeline history showing nothing was
ever wrong, which is precisely the failure mode this chapter's closing
gotcha (a swallowed exit code) warns against.