Conversation
TODO - review & update documentation & examples.
jgebal
commented
Oct 23, 2019
…text # Conflicts: # test/ut3_tester/core/test_suite_builder.pkb # test/ut3_tester/core/test_suite_builder.pks
Added validation of context name.
Member
Author
Changed behavior of ``--%context` annotation. The value f annotation now only indicates the context description. Resolves #1016
Member
Author
Member
|
I see that it's implemented but I think that nested context is misuse. I think it should be replaced by nested suites and context should be not nested and exists within a suite. I will look into code 👍 |
Member
Author
|
I was of the same opinion from the moment we originally discussed contexts. |
lwasylow
approved these changes
Nov 1, 2019
This file contains hidden or 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
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.
Added ability to nest contexts in suites - Resolves #938
Added fix for invalid context name - Resolves #966
Changed approach for context naming - Resolves #1016
So now you can write tests like a Pro (see talk by Kevlin Henney)
Leading to