Replies: 2 comments 1 reply
-
@davidgm0 thanks for the suggestion. I'll think about it but can't promise any timeline on this. I'll review Guard and their Guardfile. It would be nice if this could be possible without being too intrusive. A current workaround is to use the forced selection to run multiple test files on change. This feature isn't smart to use patterns and a new forced selection should be defined when switching models. I'll try to source multiple Guardfiles to see whether there is a general pattern that developers are using with guard. |
Beta Was this translation helpful? Give feedback.
-
I haven't had the time to look into this but I plan a new release in the near future and will be looking into this idea. My current 2cent are some options to provide a mapping test rules
This would allow some customisation while keeping in Retest philosophy of not having to change a repository to start testing if necessary. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I know one of the benefits of retest is not having configuration, but I was wondering if it'd be an option to allow to configure this. With the
Guardfile
this is possible. I'm not saying it has to work exactly like that, but it'd be nice to have something like:If the model
User
changes, also run the User controller. Not all the users may want that, but in some cases yes. There can also be some arbitrary folders (likeservices
) that you may also want to test.Beta Was this translation helpful? Give feedback.
All reactions