-
Notifications
You must be signed in to change notification settings - Fork 187
Feature/nested context #1013
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/nested context #1013
Conversation
TODO - review & update documentation & examples.
…text # Conflicts: # test/ut3_tester/core/test_suite_builder.pkb # test/ut3_tester/core/test_suite_builder.pks
Added validation of context name.
Changed behavior of ``--%context` annotation. The value f annotation now only indicates the context description. Resolves #1016
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 👍 |
All reactions
Sorry, something went wrong.
I was of the same opinion from the moment we originally discussed contexts. |
All reactions
Sorry, something went wrong.
Successfully merging this pull request may close these issues.
Consistent syntax for suite/test/context annotations Use of fullstop character in --%context(<name>) Nested Contexts to allow easier hierarchical tests
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