Dir and FileList have undefined order, so sorting them is strictly better than not. Sorting should not have a performance impact in any realistic use case: Sorting 100k shuffled elements is near-instantaneous, and sorting 1M elements takes ~3 seconds, so file system access time will always dominate. One particular reason why this is useful is that undefined ordering is a major source of flickering test suite failures.
- not in the context of config - aligns with shared_examples_for API - also add `include_context` method to example group - so shared context can be included ... - using include_context - by matching metadata
- also removed obsolete experimental cuke feature
The existing implementation eval'd the block twice: once using instance_eval_with_args (to deal with eval'ing the block with arguments) and once using module_eval (to extract the instance method definitions). This had a number of problems that the new implementation avoids. Note that this new implementation does have an undesirable side effect: all method definitions (either instance or class) in a shared example group will be defined as instance _and_ class methods. I don't see any way around this, unfortunately. A fuller discussion of this can be found on the mailing list: http://groups.google.com/group/rspec/browse_thread/thread/612cdf821a65c296 - Closes #123.
introduced in 1.8.7).
- cleanly supports passing a block or not - does not support using super when replacing behaviour within the group
…ehave_like to call their base implementation using super.
…ethods and use the RSpec DSL for a particular instance of the shared example group.
groups. - Fixes bug introduced in 42b6846.