nebari validate unit tests

[sblair-metrostar]

Reference Issues or PRs

#1862

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe): Unit tests

Testing

• Did you test the pull request locally?
• Did you add new tests?

Any other comments?

[kcpevey]

@sblair-metrostar is this ready for review?

[sblair-metrostar]

@sblair-metrostar is this ready for review?

Yes, this is just unit tests, nothing functional. Also not intended to be 100% coverage out of the gate, just an initial set of tests that we can build on as we go. This one specifically assumes we'll want to add yaml config files over time and they'll automatically get picked up as additional test cases.

[iameskild]

Thanks @sblair-metrostar for the testing updates!

As I mentioned to you offline, we might want to try and write a fixture that generates these config files but this is something we can tackle in the future; I've added it to the testing improvements meta issue.

[iameskild]

Related to #1955