Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[vitest-angular] watch mode does not pick up file changes for files created after the watch mode starts #1516

Open
2 tasks
R-Bower opened this issue Dec 20, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@R-Bower
Copy link

R-Bower commented Dec 20, 2024

Please provide the environment you discovered this bug in.

"@analogjs/platform": "~1.10.3",
"@analogjs/vite-plugin-angular": "~1.10.3",
"@analogjs/vitest-angular": "~1.10.3",

Which area/package is the issue in?

vitest-angular

Description

When you create a new spec file in watch mode, vitest detects it but immediately emits an error:
Error: No test suite found in file.

Even if you add the vitest imports and create test cases, this error will not change until the watch session is restarted.

Please provide the exception or error you saw

`Error: No test suite found in file`.

Other information

No response

I would be willing to submit a PR to fix this issue

  • Yes
  • No
@R-Bower R-Bower added the bug Something isn't working label Dec 20, 2024
@R-Bower R-Bower changed the title watch mode does not pick up files created after the watch mode starts [vitest Angular] watch mode does not pick up files created after the watch mode starts Dec 20, 2024
@R-Bower R-Bower changed the title [vitest Angular] watch mode does not pick up files created after the watch mode starts [vitest-angular] watch mode does not pick up files created after the watch mode starts Dec 20, 2024
@R-Bower R-Bower changed the title [vitest-angular] watch mode does not pick up files created after the watch mode starts [vitest-angular] watch mode does not pick up file changes for files created after the watch mode starts Dec 20, 2024
@brandonroberts
Copy link
Member

brandonroberts commented Dec 20, 2024

I tested this and got this same behavior also. After I hit the enter key, it picked up the newly created test

@R-Bower
Copy link
Author

R-Bower commented Dec 20, 2024

interesting, I'll try this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants