You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the code base lacks any form of testing - Pester tests should be developed to help keep development stable and ensure that functionality is not impacted when making any changes.
The text was updated successfully, but these errors were encountered:
I think a good follow on for this would be creating a CI pipeline to run pester tests for new PRs. Ensures that the tests pass before being able to merge any changes to master.
I think a good follow on for this would be creating a CI pipeline to run pester tests for new PRs. Ensures that the tests pass before being able to merge any changes to master.
Definitely - that's my current plan. I'm going to work through creating tests where possible for most of the checks and then setup a CI workflow using GitHub Actions.
Currently, the code base lacks any form of testing - Pester tests should be developed to help keep development stable and ensure that functionality is not impacted when making any changes.
The text was updated successfully, but these errors were encountered: