Skip to content
This repository has been archived by the owner on Mar 16, 2024. It is now read-only.

Split make test target #1820

Merged
merged 1 commit into from
Jun 21, 2023
Merged

Split make test target #1820

merged 1 commit into from
Jun 21, 2023

Conversation

njhale
Copy link
Contributor

@njhale njhale commented Jun 21, 2023

Split make test target into separate unit and integration targets.

Signed-off-by: Nick Hale 4175918+njhale@users.noreply.github.com

Split make test target into separate unit and integration targets.

Signed-off-by: Nick Hale <4175918+njhale@users.noreply.github.com>
Copy link
Contributor

@tylerslaton tylerslaton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had a comment about breaking these tests out into their own jobs for a few reasons. It isn't blocking though and I could see this going in as is.

Comment on lines +33 to +34
- run: TEST_FLAGS="--junitfile test-summary.xml" make unit
- run: TEST_ACORN_CONTROLLER=external TEST_FLAGS="--junitfile test-summary.xml" make integration
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What would your thoughts be on breaking out these two steps into their own jobs? I see a few benefits here:

  1. Unit tests shouldn't (at least in theory) need an Acorn installation or image built. So the separated Unit job can ignore those parts.
  2. The Unit and Integration tests can run in parallel which would speed up the feedback loop.
  3. Each test type gets their own summary.

The main con is that we increase the amount of action minutes we use but not by that much.

Copy link
Contributor Author

@njhale njhale Jun 21, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Totally agree that we should break this out into two distinct jobs. I chose this route for now because we effectively still get two separate go test runs with separate timeouts, but without the hassle of rewiring the test output/slack reporting or starting a new runner.

I was thinking about doing that as a follow up. WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep! Sounds good to me. Totally fine with this being a follow-up.

@njhale njhale requested a review from g-linville June 21, 2023 15:12
@njhale njhale merged commit 4a2e878 into acorn-io:main Jun 21, 2023
2 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants