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

retest not recognising spec files as specs when modified. #11

Closed
gstamp opened this issue Sep 9, 2020 · 1 comment · Fixed by #12
Closed

retest not recognising spec files as specs when modified. #11

gstamp opened this issue Sep 9, 2020 · 1 comment · Fixed by #12
Labels
bug Something isn't working
Projects

Comments

@gstamp
Copy link

gstamp commented Sep 9, 2020

Say I have some files with the following paths:

<project root>/app/lib/module/myfile.rb
<project root>/spec/module/myfile_spec.rb

retest will find the spec if I modify myfile.rb but If I modify myfile_spec.rb it reports: "Could not find a file test matching" (the wording of that feels a little off).

The behaviour I'm expecting is that retest realises this is a spec and just runs it directly.

@AlexB52
Copy link
Owner

AlexB52 commented Sep 10, 2020

Sorry for late reply, I did not see the Github notification. That is a good point @gstamp. The behaviour and wording should be updated.

In the meantime, a workaround is to first save the myfile.rb which will run the spec myfile_spec.rb then you can modify your spec file myfile_spec.rb.

The behaviour is that retest will rerun the last command run when no specs are found.

@AlexB52 AlexB52 added this to To Do in v1.0.0 via automation Sep 10, 2020
@AlexB52 AlexB52 added the bug Something isn't working label Sep 10, 2020
v1.0.0 automation moved this from To Do to Done Sep 12, 2020
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
No open projects
v1.0.0
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants