A *very* seasoned software engineer, I wrote my first basic game, a lunar landing game, in Basic in 1969. Currently I am doing web development in Ruby on Rails, JavaScript, Elm.
Hmm that's interesting. What's bisecting? Is that the default that comes with running the rspec command? I'm using a bin command that's runs plain rspec, and now that I think about it I haven't tried running the entire test suite in guard.
Edit: No luck in guard, and judging from our bin/rspec command, doesn't seem like we are bisecting either. The investigation continues...
A *very* seasoned software engineer, I wrote my first basic game, a lunar landing game, in Basic in 1969. Currently I am doing web development in Ruby on Rails, JavaScript, Elm.
rspec bisect is so very cool. let's say running in CI, you had some failures, and you want to find out if they happen to be order-dependent, or if there's a root of something failing. You pass the test command, with the seed the tests were run with and the --bisect command, and rspec will find the minimal set of tests that need to run in order to reproduce the set of failures; hopefully winnowing down where the actual failure is coming from! Definitely a useful part of the rspec toolbelt
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm seeing a segfault when I try to bisect a series of tests. I'm already running 2.5.1. Running rspec without the bisect works fine.
Hmm that's interesting. What's bisecting? Is that the default that comes with running the
rspeccommand? I'm using abincommand that's runs plainrspec, and now that I think about it I haven't tried running the entire test suite in guard.Edit: No luck in guard, and judging from our
bin/rspeccommand, doesn't seem like we are bisecting either. The investigation continues...rspec bisect is so very cool. let's say running in CI, you had some failures, and you want to find out if they happen to be order-dependent, or if there's a root of something failing. You pass the test command, with the seed the tests were run with and the
--bisectcommand, and rspec will find the minimal set of tests that need to run in order to reproduce the set of failures; hopefully winnowing down where the actual failure is coming from! Definitely a useful part of the rspec toolbelt