[BUG] @nx-dotnet/core:test watch option is not working as expected

[mxa0079]

Describe the bug
According to the documentation there is a watch option that would determines if dotnet test or dotnet watch test is used to execute tests.

However, this option results on the wrong command being invoked and it does not work as expected

To Reproduce
Steps to reproduce the behavior:

1. Generate a new dotnet project with a corresponding xUnit test project
2. Run the test executor for this unit test project, confirms it runs as expected
3. Open project.json for the test project and add the watch option:

"test": {
     "executor": "@nx-dotnet/core:test",
     "options": {
       "watch": true //The watch option
     }
   },

5. Try to test the project in watch mode and watch the wrong command being invoked:

Executing Command: dotnet "--project" "/testporjectpath/Project.Test.csproj" "test"
Unknown option: --project

Expected behavior
To run the test project in watch mode

Screenshots
NA

Environment:

• OS: MacOs Monterrey
• Browser NA
• Version .net 5

[AgentEnder]

Hey @mxa0079! Thanks for the report, it looks like this wasn't covered by our tests and was subsequently missed when changing over to use spawn.

[github-actions]

🎉 This issue has been resolved in version 1.9.12 🎉

The release is available on:

• v1.9.12
• GitHub release

Your semantic-release bot 📦🚀

[mxa0079]

Thanks @AgentEnder for the prompt reply.

Ive updated to version 1.9.12 - the project now runs with the watch = true option however it does not run on watch mode. Hence, I request to re-open the issues.

[AgentEnder]

@mxa0079 I can't replicate the behavior you are describing.... running nx test {project}-test --watch launches the tests and retests when a file changes. Can you give more details to the errors you are seeing? Maybe some screenshots of terminal outputs could help.

[mxa0079]

My bad, things are working now. Thanks for your help! Fantastic response time, kudos to the whole team. Have a wonderful week!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.