Improve experience on writing unittests #570
Reference in New Issue
Block a user
No description provided.
Delete Branch "refs/pull/570/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While working on #409, I noticed that some unittests contains either
invalid assertion methods (
isNotEmpty
) or invalid properties (any
)for a specific assertion method (
notContains
).As our tests pass - and I have ensured that they can fail - this seems
related to the YAML schema validation in the IDE.
I've noticed that
isNotEmpty
was replaced byisNotNullOrEmpty
1in version v0.3.22. At least from a schema validation point of view.
It is still working. Maybe deprecated? I don't know.
Regarding the
any
property, the documentation seems incorrect. I'vefiled a PR for it3. As soon as that PR is merged and released, we
could probably validate the test YAML files in our PR workflow.
Last, since we renovate the used helm-unittest version, we should also
renovate the used YAML schema file.
https://github.com/helm-unittest/helm-unittest/pull/139 ↩︎
https://github.com/helm-unittest/helm-unittest/releases/tag/v0.3.2 ↩︎
https://github.com/helm-unittest/helm-unittest/pull/243 ↩︎
Nice find.
I guess renovate won't be able to fetch schema diffs in the changelog but anyhow - surely good to fix it!
Yep, Renovate most likely doesn't detect those changes. But we will receive one single dependency bump for all occurrences of the unittest plugin. And that should have the changelog from its GitHub release.