Skip to content

Conversation

@cwaldren-ld
Copy link
Contributor

No description provided.

description: 'The target test framework to use.'
required: false
default: 'net6.0'
test_verbosity:
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Without this, it just appears like the tests are hanging in CI. I can see the value of not having this when running locally, but it's nice to have the record when waiting remotely.

run: |
dotnet restore ${{ inputs.test_project_file }}
dotnet test --framework=net6.0 ${{ inputs.test_project_file }}
dotnet test -v=${{ inputs.test_verbosity }} --framework=${{ inputs.target_test_framework }} ${{ inputs.test_project_file }}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Previously, it was passing net6 as the framework. I believe this was causing it to silently just not run tests at all. The target for the client tests is net7.

@cwaldren-ld cwaldren-ld marked this pull request as ready for review October 25, 2024 17:40
@cwaldren-ld cwaldren-ld requested a review from a team as a code owner October 25, 2024 17:40
@cwaldren-ld cwaldren-ld merged commit 6d82447 into main Oct 25, 2024
8 checks passed
@cwaldren-ld cwaldren-ld deleted the cw/client-unit-tests branch October 25, 2024 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants