-
Notifications
You must be signed in to change notification settings - Fork 45
Port old tests #105
Comments
People without write access do not seem to be able to self-assign issues. |
I went through the old tests (thanks @brianbunke for the link!) and created the following table to help focus on what tests are remaining. I'll continue to update the table as more tests are added, noting what changes are made. This list includes the Task and Event tests created by @jeffgreenca in #106. If there are any I missed from the old or missed new additions please let me know and I'll update.
|
I'll take the two Net Dump Configuration items if they're still unclaimed. |
I think i should be able to knock out most of these except for the Network scope. |
I'll work on the VM snapshot test next. |
That's awesome, thanks. Plan on taking some tests on myself once I get back to a more regular routine. This is more of a reminder to myself, but reference this issue in your PR when submitted. |
Going through the table posted by @haberstrohr I believe all of these tests have been ported. Can someone confirm? |
Host: NFS Advanced Config? |
As @boyler05 pointed out in #91, we never got around to porting all of the old tests into the new format. I'd prefer others work on this, so I'm labeling it up for grabs. If you're interested, please speak up and I'll assign. (Random GitHub question: Can people w/o write access to the project self-assign issues?)
Happy to answer any questions and provide guidance if needed.
EDIT: This needs more info.
Here's a snapshot of the repo in the old test format: https://github.com/WahlNetwork/Vester/tree/47f400a76738d28308881f0573526ebc14f3885e
I believe all the tests pointed out existed at that time. You would need to:
Config.ps1
(for at least the$Desired
value) andConfig.Tests.ps1
(for at least the$Description
) to grab related values.Vester.ps1
file and update the variablesAt this point, we generally name tests "Category-Specific.Vester.ps1". We haven't implemented anything that cares about that right now, but it's a decent way to group tests together, especially during a
Get-ChildItem
.The text was updated successfully, but these errors were encountered: