describe blocks not executing in order #28
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! I'll take a look when I get home tonight |
andyjones
added a commit
that referenced
this pull request
Jul 27, 2015
describe blocks not executing in order
|
Thanks, 0.51 should be on cpan shortly |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi. Thanks for Test::Spec. It's really helping to make my tests more readable.
I think I found a problem in the order that blocks are executed, unless I'm missing something.
Looks like the top-level containers in the %_Package_Contexts do not have have their order maintained.
I added a test, t/ordering.t, that demonstrates the problem.
All I did was change it to use the _ixhash() function to create those containers rather than a naked hash.