Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unit Tests don't run locally or in CI #17

Closed
TraGicCode opened this issue Apr 13, 2018 · 0 comments · Fixed by #16
Closed

Unit Tests don't run locally or in CI #17

TraGicCode opened this issue Apr 13, 2018 · 0 comments · Fixed by #16

Comments

@TraGicCode
Copy link
Contributor

Because of the way the test file is named it's not actually running under appveyor and locally running a simple invoke-pester ./Tests/ is not identifying the file because it ends in .test.ps1 instead of .Tests.ps1
@TraGicCode TraGicCode mentioned this issue Apr 13, 2018
Merged
johlju pushed a commit that referenced this issue Apr 20, 2018
@TraGicCode @johlju
Unit Tests not running because of naming convention. (#16)
8be95b9 
- Fixed bug in which unit tests were not being run and also when run would have failed (issue #17).
  - Fixed PSSA issues as well.
  - Fixed Markdown linting issues as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Unit Tests not running because of naming convention.
1 participant
@TraGicCode