-
Notifications
You must be signed in to change notification settings - Fork 11
Ensure we're testing module functions and logic #66
Copy link
Copy link
Open
Labels
0 - BacklogIssue is accepted, but is not ready to be worked on or not in current sprint.Issue is accepted, but is not ready to be worked on or not in current sprint.BugIssues where something has happened which was not expected or intended.Issues where something has happened which was not expected or intended.
Milestone
Metadata
Metadata
Assignees
Labels
0 - BacklogIssue is accepted, but is not ready to be worked on or not in current sprint.Issue is accepted, but is not ready to be worked on or not in current sprint.BugIssues where something has happened which was not expected or intended.Issues where something has happened which was not expected or intended.
Type
Fields
Give feedbackNo fields configured for issues without a type.
What You Are Seeing?
Many tests shadow the actual module function with an ad-hoc function that does nothing and only the tests use. As a result, there aren't really any tests for the module logic itself.
What is Expected?
Tests should be verifying the module behaves as intended given various inputs and outputs of mocked functions.
How Did You Get This To Happen? (Steps to Reproduce)
See for example:
ChocoCCM/src/Tests/computer.tests.ps1
Lines 1 to 11 in 2c92049
System Details
N/A
Output Log
N/A