Integration tests with Aspire on CI runner

[Kralizek]

In my team we're discussing the possibility to run a suite of tests targeting an instance of our system running on the CI runner.

In previous projects, I was using an ad-hoc docker-compose file to spin the whole system via docker compose up -d, then run the tests and finally kill everything.

Is there a way to have dotnet run return to the console when the AppHost has complete starting the system?

[davidfowl]

Are you thinking about using the built in integration testing support, or something else?

[Kralizek]

Uhm no, I was thinking about doing something like:

& dotnet run AppHost
... (Wait for application to be running)
$env:target = url
dotnet test
kill AppHost 

I didn't think about the testing support because In my head it was used to test integrations. Or?

[tombrewer-onwave]

@davidfowl - is it now possible to be able to execute 'local' (containerised) integration tests (beyond the developer machine running Aspire) from within a CI pipeline (e.g. Git Actions)? For example previously I've used Testcontainers to automatically handle the lifecycle of an Azurite container and run a limited integration test in-line from a normal MSTest project (with dotnet test). I'd like to replace that with an Aspire solution so I don't have to configure the dependencies twice (once for local Aspire hosting, and again for running Testcontainer based tests in CI).

[tombrewer-onwave]

I'll answer my own question - I can confirm I am able to run Aspire based localised integration tests within a Github CI pipeline with just regular Dotnet Test (without any special set-up) if that helps anyone else. The environment wasn't particularly complex but I was able to use the DistributedApplicationTestingBuilder pretty easily. I did have to pick up and map some app config (e.g. a dynamic connection string which Aspire generates) from the DistributedApplication instance to add to the dependency injected IConfiguration on initialization - I don't know if that's the correct way but it worked.

[lopezbertoni]

I was never able to get this running (#9452)
Can you maybe shed some light on what tests are you running?
Everything works locally for me, it's just the pipeline that chokes.
Thanks in advance.

[Hypothesys-Smithgor]

Very interested in this one - been trawling for examples or guidance but not finding anything at all.
I'm a Github Actions newbie, so I've started very basic - created the Aspire sample app including default xUnit test (GetWebResourceRootReturnsOkStatusCode - just tests the health of the webfrontend).
This runs fine locally, but when I try to run as part of github actions it fails - seems to be at the point where I attempt to start Host.DistributedApplication ( await app.StartAsync(cancellationToken).WaitAsync(DefaultTimeout, cancellationToken); ) it times out.
If anyone has any ideas how I get past this step, I'd be hugely grateful!