-
-
Notifications
You must be signed in to change notification settings - Fork 468
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
Any support for tags on Context blocks planned? #657
Comments
It's something we've talked about, but surprisingly hard to implement. It might not make it into the v4 release, but is something we can look at later on as an enhancement. |
I see that in the function Context.ps1 is added the parameter Tag. But based on the line 129 in the Describe.ps1 I assume that tags are only supported for Describe. Am I right? |
In v4, there's really no difference between the |
Hi there, just wondering is it possible that these tags as @davidwallis3101 mentioned for this issue be useful as a TODO list which a set of several contexts required for one Describe block. Then later run a small summary script to see how many "to do" tests are outstanding for reflection purposes. Thanks. I had asked the pester group forum for some ideas https://groups.google.com/forum/m/#!topic/pester/fwMtDsILe4k |
@PeterMTaylor You can use |
Implemented in v5. |
As above really..
I do describe "server intergration tests"
Context 2016
Context 2012
Context 2008
Context Linux
And a lot of my initial pre-reqs and setup are under the describe block.. but Id rather not do multiple describes, but if necessary..
The text was updated successfully, but these errors were encountered: