Running Full System Acceptance Tests as Part of a Command Line Build – PwP Episode 13

Challenges

  • Automating full system acceptance tests within a command-line build process.
  • Ensuring test reliability across diverse environments.
  • Reducing delays caused by testing inefficiencies in build pipelines.

Solutions

  • Integrating full system tests into command-line build workflows.
  • Using robust tools to handle cross-environment compatibility.
  • Streamlining test execution to minimize build time impact.

Benefits

  • Faster deployment cycles with integrated testing.
  • Increased confidence in production readiness through automated validation.
  • Consistent and repeatable test outcomes across builds.

In this episode, Jeffrey is going to look at the full system acceptance test suite that was created in the last episode and get it running a command line. This will include prepping it to run in a build.

Code sample: https://github.com/jeffreypalermo/onion-architecture-dotnet-6/

You will begin by making it possible to run your private build on your local workstation by running click-to-build dot bat just by running your PowerShell build script. It’s great to launch the application locally and then go over to in-unit or ReSharper or the Visual Studio test runner and run the test suite, but we want it convenient. We want to make sure it is convenient for the developers on our team. If it is not convenient, developers on the team won’t run it all the time. We want the developers on our team to run it all the time. This is done by making it a single command or a single DoubleClick.