Skip to content

README.md

Latest commit

 

History

History
44 lines (38 loc) · 1.81 KB

README.md

File metadata and controls

44 lines (38 loc) · 1.81 KB
Raw

Integration Tests

This directory contains Concord's integration test modules.

Commands:

  • Full docker-profile build without tests: 
    ./mvnw clean install -Pdocker -DskipTests
  • Single console integration test with Docker-managed dependencies: 
    ./mvnw -pl it/console verify -Pit -Pdocker -Dit.test=LoginIT

The -Pdocker IT flow uses the locally built walmartlabs/concord-server and walmartlabs/concord-agent images, along with their upstream dependencies. If you changed those areas, rebuild first with the full docker-profile command above before running it/console.

Notes:

  • Integration test resources are part of the regression surface. Prefer adding new flows or fixtures for additional coverage instead of changing existing flows. Modify an existing flow only when the previous behavior is explicitly no longer supported, or when the fixture itself is incorrect, and document the reason in the corresponding change.
  • The single-test command starts Postgres, Concord Server, Concord Agent, and Selenium via Docker.
  • The first LoginIT run may need to pull browser images, so it can be noticeably slower than subsequent runs.
  • Failing it/console tests write screenshots to it/console/target/screenshots/.
  • New test modules should prefer testcontainer-concord instead of the older setup pattern used in it/server.
  • it/agent-operator deploys the agent operator into a k3s testcontainer. It requires the locally built walmartlabs/concord-server, walmartlabs/concord-agent and walmartlabs/concord-agent-operator images (see the docker-profile command above). Run it with: 
    ./mvnw -pl it/agent-operator verify -Pit -Dit.test=AgentOperatorIT
  • For broader context on prerequisites and the general -Pit flow, see ../README.md.