Skip to content

Day 6 — Newman and GitHub Actions Automation

Choose a tag to compare

@daryal89 daryal89 released this 06 Aug 18:41
· 3 commits to main since this release
e333812

Overview

This release adds command-line and continuous-integration API testing to
the completed manual, REST API and PostgreSQL testing portfolio.

Day 6 Highlights

  • Added Newman as a project dependency
  • Executed the complete Postman validation suite through Newman
  • Added a stable 19-request CI smoke/regression collection
  • Executed 45 passing CI assertions
  • Added GitHub Actions automation
  • Protected demonstration credentials with repository secrets
  • Generated JSON and JUnit reports
  • Preserved separate smoke and full-validation workflow artifacts
  • Retained all Day 5 test expectations and confirmed-defect evidence
  • Added CI coverage mapping, execution reporting and troubleshooting
    documentation
  • Replaced duplicate warning annotations with one informational notice
  • Added final successful main workflow evidence

Verified CI Results

Metric Result
CI requests executed 19
CI test scripts executed 19
CI pre-request scripts executed 2
CI assertions executed 45
CI assertions passed 45
CI assertions failed 0
CI runtime errors 0
Complete validation requests 26
Complete validation test scripts 26
Complete validation assertions 61
Complete validation assertions passed 51
Known complete-suite failures 10
Complete-suite runtime errors 0
GitHub Actions quality gate Pass
Automated report formats JSON and JUnit
Workflow artifact groups 2

Testing Strategy

The stable CI smoke/regression collection is the strict passing quality
gate.

The complete validation collection preserves positive, negative,
boundary, authorization and confirmed-defect coverage. Its 10 known
failed assertions remain visible without overriding a successful CI
quality gate.

The final workflow displays one expected error annotation from Newman's
nonzero complete-suite exit code and one informational notice explaining
the documented requirement mismatches.

Confirmed API Findings

  • Invalid booking-date sequences are accepted during creation and update
  • Zero and negative total prices are accepted
  • Missing required fields return HTTP 500 instead of a clear HTTP 400 or
    HTTP 422 client-validation response

Security

  • Public environment credentials remain blank
  • Local environments remain excluded from Git
  • GitHub Actions credentials use repository secrets
  • Active tokens are not committed
  • Generated local Newman results remain ignored
  • Public screenshots and exports were reviewed for sensitive values

Previous Baseline

The Day 5 manual, API and database testing baseline remains available as
release v1.0.0.