-
Notifications
You must be signed in to change notification settings - Fork 188
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
Add tests to GitHubRepositories.tests.ps1 #176
Add tests to GitHubRepositories.tests.ps1 #176
Conversation
Add tests for GitHubRepositories.ps1 functions
Thanks, @themilanfan! I'll take a look at this over the weekend. |
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.
Thanks for the submission, @themilanfan! Much appreciated!
Are you sure that you ran this iteration of the tests? There are a number of issues with them that should have caused failures. I added notes for a lot of them, but then I stopped looking further.
Try merging in the most recent changes in master and then take a stab at updating these tests again and make sure that they all pass. It's possible that you have some local default configuration for DefaultOwnerName
and DefaultRepositoryName
which is confusing things, however Common.ps1
should have swapped that out with the default configuration during test execution.
I'll leave it to you to investigate these a bit more.
Looking forward to future updates.
Remove -Verbose, parenthesis, and s from Topics
Pending merge of issue #174 once it's merged to master so I can add the missing -Confirm:$false |
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.
Thanks for the update, @themilanfan. It looks like there are still some issues to address. I didn't thoroughly look through this yet. I suggest that you run the tests all locally as well in a clean PowerShell session to try and see some of the issues that I'm point out.
Thanks again for all your hard work. Looking forward to your next update!
@HowardWolosky Sorry I wasn't explicit, I plan on testing and fixing the kinks once #174 gets merged so I can include the missing -Confirm:$false. However, I will fix the other things you noticed in the meantime 😄 I'll make sure next time to be clear so I can help you avoid reviewing for nothing! |
Added remaining -Confirm:$false following new merges that added -Confirm:$false functionality.
[WIP] Pending testing |
@HowardWolosky almost all is fixed, I'm getting one error for a test involving clearing repository topics. Could it be a bug? When i ran the
|
@HowardWolosky should be good for review following issue raised & PR from @X-Guardian (thanks!). |
Finding that bug (#215) is a fantastic outcome to this PR. I love that by writing some missing UT's we identified an actual bug in the module, and that we now have a UT to catch further regressions of that area in the future. Thanks again! |
@HowardWolosky can confirm all tests pass now since #216 was merged |
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.
Thanks for the great update.
Two minor fixes (one logic error, and one comment fix that I would have ignored if the logic error hadn't been there too) and this will be ready to go.
Co-authored-by: Howard Wolosky <[email protected]>
Co-authored-by: Howard Wolosky <[email protected]>
Changes committed 👍 @HowardWolosky |
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Awesome. Running CI build now to verify, then will merge in. Thanks again!
Your CI build failed due to static analysis failures:
Please verify static analysis is passing before submitting your next update. Thanks! |
@HowardWolosky apologies, will be more careful for next one. I've followed the same method other tests use to avoid this issue. Ready to re-run |
No worries. We had a bunch that had snuck in over time that I recently addressed (#180). That's why I got the CI build healthy again...to help keep master clean. And it looks like #193 also just failed for static analysis failures too, so you're in good company. Will kick off a new CI build now. |
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
There was one failing test, but only on macOS, and it was in Project Cards (unrelated) which means that there was something flakey going on.
Merging this in now. Thanks for all your efforts! 🎆 |
Fixes #139
Add tests for GitHubRepositories.ps1 functions