-
Notifications
You must be signed in to change notification settings - Fork 63
Conversation
/cc @muratg @davidfowl @victorhurdugaci @troydai @Eilon |
param( | ||
[string]$PesterPath = $null, | ||
[string]$PesterRef = "anurse/teamcity", | ||
[string]$PesterRepo = "https://github.com/anurse/Pester", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will probably need to find a new home before we merge :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll need to either contribute my change back to Pester or put our own fork up on aspnet. It's a pretty minor change, I can look at having it integrated if you're up for it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Saw your email, will discuss there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR is out! pester/Pester#243 - Looking good for integration
8973f86
to
e5fc557
Compare
7518f41
to
86e422e
Compare
This has been merged in to dev. Not sure why the PR didn't close... |
Probably because you didn't update the server branch after you rebase and squash. |
Added a bunch of automated tests using Pester.
Note: I needed to patch Pester to write marker strings to stdout for TeamCity to read (as per https://confluence.jetbrains.com/display/TCD9/Build+Script+Interaction+with+TeamCity). The patch is in a personal fork of Pester.
It's all integrated into the makefile, so it works on the CI and reports detailed test failure information to the Tests tab for the build on TeamCity.
There are a couple scenarios that are not covered (they involved a lot more machine-level config I didn't want to mess with in automated tests):