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
{{ message }}
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.
I get that having logical comparisons in typical unit tests isn't a good idea,
ie a totally crappy example:
if ($name.StartsWith("blahblahblah")) {
it "something" {
$name | should match "blah*"
}
}
else {
it "blah" {
$name | should match "foo*"
}
}
which I could also do with a single regex ie: blah.|foo. - however this would allow for wrong 'combinations'
but I have specific whole comprehensive tests that I dont want to run in a cloud based test but do in a on prem test and I also have the odd test where I expect different results based on the name of the machine. I also want to use the same set (module) of tests..
Thoughts on how to do this?
conditional logical
conditional logic by means of a function to do the verification which has its own tests?
Name the tests and then only execute tests with a specific naming convention?
Thanks
David
The text was updated successfully, but these errors were encountered:
I added Pester tag support in PR #16 so you can query for and execute tests based on tags (include or exclude). These changes are not in a published version of OVF unfortunately. You'll have to pull down this repo and manually import the module (the \OperationValidation subfolder). The latest version in source is 1.1.0 and what is published is 1.0.1.
Ahh ok if it supports tags then I will use that version 👍
Any ideas when the gallery is likely to receive these updates as it would make my internal deployment easier as my internal repo pulls from PSGallery and I dont want to manually push to the internal gallery.
I get that having logical comparisons in typical unit tests isn't a good idea,
ie a totally crappy example:
which I could also do with a single regex ie: blah.|foo. - however this would allow for wrong 'combinations'
but I have specific whole comprehensive tests that I dont want to run in a cloud based test but do in a on prem test and I also have the odd test where I expect different results based on the name of the machine. I also want to use the same set (module) of tests..
Thoughts on how to do this?
Thanks
David
The text was updated successfully, but these errors were encountered: