So the idea here is that some tests "pollute" other test cases because they have side effects; leave traces of their run in the system.
My initial reaction would be that in the BEAM and Elixir this issue is not so prominent as in other more dynamic languages, because we (in general) don't do monkeypatching or other crazy runtime stuff, and database tests are already isolated from each other through the sandbox. However I have been bitten by this in some cases, for instance depending on `Application.get_env`, or on which OTP applications are started or stopped. In general, having issues like this is a symptom of having test cases that do not clean up after themselves like they should, I believe. I'm not sure that this should be a part of the core. Arjan On Wednesday, April 17, 2019 at 8:03:03 PM UTC+2, Paulo D Gonzalez wrote: > > Hi Andrea! Thanks for the quick reply. > > Here is some info on bisect: > https://relishapp.com/rspec/rspec-core/docs/command-line/bisect > > Here is where the implementation of the lib I used to use: > https://github.com/rspec/rspec-core/tree/master/lib/rspec/core/bisect > > This was useful when tests would fail in a mysterious way. This would give > us some added introspection when it succeeded. It felt like a `git bisect` > that was done automatically for you. > > On Wed, Apr 17, 2019 at 12:52 PM Andrea Leopardi <[email protected] > <javascript:>> wrote: > >> I can't recall if this has been discussed before but I don't think it >> has. Could you expand in more detail what --bisect does? >> >> Andrea Leopardi >> [email protected] <javascript:> >> >> >> On Wed, Apr 17, 2019 at 7:38 PM Paulo D Gonzalez <[email protected] >> <javascript:>> wrote: >> >>> In my previous life ( :) ) I was able to use something that would be >>> equivalent to `mix test --bisect --seed 776` and it used to be very helpful >>> when dealing with a big codebase with crazy test failures. >>> >>> I was wondering what are your thoughts on this feature in Elixir? I >>> tried looking at existing discussions on this and didn't find any. If there >>> are, could you please point me to it? >>> >>> Thank you. >>> >>> Paulo >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "elixir-lang-core" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elixir-lang-core/7bf0827d-1174-4aec-ba08-58e88de6c2de%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/elixir-lang-core/7bf0827d-1174-4aec-ba08-58e88de6c2de%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "elixir-lang-core" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elixir-lang-core/rv1A8x4DBvo/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elixir-lang-core/CAM9Rf%2BKwSfrMgwM%2B42J3bNK-fpY3%3D0Ls5yRZVN%2BCJkaWYBUobg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/elixir-lang-core/CAM9Rf%2BKwSfrMgwM%2B42J3bNK-fpY3%3D0Ls5yRZVN%2BCJkaWYBUobg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/e006ad91-8794-48e9-a969-9d53a2ecf788%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
