Replies: 7 comments 17 replies
-
First observation, when using EDIT: This can currently be solved by remote debugging since the test is run in another process To use debugger with retest v2.0.0.pre # In your app
require "debug/open_nonstop"
debugger # somewhere in your code Then when retest is waiting for a connection do |
Beta Was this translation helpful? Give feedback.
-
New observation
Also when entering
|
Beta Was this translation helpful? Give feedback.
-
Thanks for creating and maintaining this gem, @AlexB52 - I love it! I observed a very minor issue this morning: I ran a session with Line 31 in cd8ab0b input.gets returned nil. Unfortunately I cleared the output, so no logs, etc.
|
Beta Was this translation helpful? Give feedback.
-
I've pushed the new pre-release, 2.0.0.pre1. It should allow the use of the debugger without requiring a remote |
Beta Was this translation helpful? Give feedback.
-
Pausing the program from automatic listening is reenabled after a spec is run manually, it shouldn't until we manually reenable it. |
Beta Was this translation helpful? Give feedback.
-
Major milestone achieved. I think we're nearly ready for proper v2 release. Things left to do
You can play with the retest interactive command by installing the latest pre version with |
Beta Was this translation helpful? Give feedback.
-
Hey @AlexB52 thanks for the awesome gem, I have wanted this for a long time! Quick question for you - I have some cases where the rspec file is very large so I want to only run an example at a specific line number. How would I do that? I've tried the force command , then selected a file, but couldnt figure out how to add a line number onto the end |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I've released a POC for Retest V2 with an interactive command. You can install the preview with:gem install retest --pre
. Then run it withretest
. Useretest --help
to get info on available parameters when launchingretest
. For exampleretest --notify
will give you a sound feedback when tests are passing or failing. Highly recommend it!EDIT: Retest v2 has officially been released and can now be installed with
gem install retest
. More features and improvements to come in the next releases but this is in a state for an initial release with a complete new interactive shell.The gem works the same with the addition of a new prompt that lets you make a few commands (to be expanded in other releases)
Entering
'h'
prints the current usage of the interactive POC.Note: It's currently impossible to alter the starting arguments through the interactive command. For example
retest --all --notify
will always default the main test command to running all tests with sound feedback.I recommend using
retest --notify
on a large codebase andretest --all --notify
on projects with a very fast test suite.Question: What do people think? Feedback would be appreciated.
Thanks, everyone.
Beta Was this translation helpful? Give feedback.
All reactions