Open lipkau opened 6 years ago
@lipkau,
Are you thinking about testing examples through a public available JIRA? imho, that should be tested on appropriate pester test for every function, as each example is unique (like add something, delete something). We cannot properly test it even for simple get commands, e.g. Get-JiraIssue. Example may be valid, but the issue won't exist.
First thought was to mock Invoke-WebRequest
.
But that would make a lot of cmdlets which expect a certain response.
running against our current cloud instance would work with a BeforeEach {}
segment to set up a common environment
Expected Behavior
CI ensures that all
EXAMPLE
s in the documentation are validCurrent Behavior
EXAMPLE
s are not testedPossible Solution
Add logic into test files for reading all examples and test them.