RSpec fails when using --pattern when $PWD has a space
Add support for .rspec-local
- We don't want to specify how the ordering is done (e.g. alpabetical) just that it is consistent. - There's no need to complicate it with random seed stuff; an example showing the files being assigned in two different orders getting the same load order is sufficient.
I recently added `--color` to my `~/.rspec` file and it broke the specs in these files since it unexpectedly picked up that config in my home directory. This fixes it so that it doesn't matter what (if anything) you have in your ~/.rspec file.
Allow task args to be passed to rspec tasks.
This moves the old "local_options" to "project_options". Signed-off-by: Sam Phippen <firstname.lastname@example.org>
…ing to feedback from alindeman
…elates to #330
…-with-metadata document using metadata with shared examples
When a shared example and a describe block have the same metadata, the shared example gets included automatically. Document this. Closes Issue #440.
…m being read
…; handle this gracefully
* Also sets the source encoding for the specs to UTF-8. For some reason, Nokogiri did not correctly parse the actual output if they were read into ASCII strings. Setting the source encoding seems to solve this, even though I thought source encoding only affected the source file itself, not encodings of I/O.