Skip to content

Rails "test:system" Rake task doesn't run any tests #188

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

Closed
chrisgibson opened this issue Aug 9, 2022 · 4 comments
Closed

Rails "test:system" Rake task doesn't run any tests #188

chrisgibson opened this issue Aug 9, 2022 · 4 comments

Comments

@chrisgibson
Copy link

I created a new Rails application (with v7.0.3.1) and generated a new system test.

With v2.0.11 of the tailwindcss-rails gem, bin/rails test:system prints the Tailwind CSS compilation output and exits (without running any tests).

If I downgrade to v2.0.10, it prints the Tailwind CSS compilation output and proceeds to run the tests.

I believe the use of exec (introduced in #181) has changed the behavior when multiple Rake tasks are involved as is the case when the test:prepare Rails Rake task is enhanced with tailwindcss:build. The process is exiting after the Tailwind CSS compilation.

@flavorjones
Copy link
Member

@chrisgibson Yup, what you're describing makes sense and we shouldn't be using exec. I'll explore replacing it putting some tests in place to prevent regressions in the rake tasks.

@flavorjones
Copy link
Member

Looks like a PR to address this has been opened at #189

@flavorjones
Copy link
Member

Release v2.0.12 · rails/tailwindcss-rails addresses this.

@chrisgibson
Copy link
Author

Confirmed. Thanks @flavorjones!

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

No branches or pull requests

2 participants