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
Any examples we add to the repo should have at least a base level of testing applied to them with each PR, e.g. making sure the structure is sound (even if we don't verify the behavior).
Actual behavior
In #10 we'll be adding types and examples, but we don't yet have any tests for them.
In Get end to end tests running against PRs #6 we'll add an initial skeleton of end to end test automation, we might want to hook in yaml tests there b/c those tests also require a running cluster
The text was updated successfully, but these errors were encountered:
I haven't found any good tooling to help automate the process for when the examples are updated (to avoid copy pasting into the markdown doc files). It would be advantageous to retain the formatting that we get by GitHub's native code fencing so I will make some utilities that will update/check the files for this purpose in addition to asserting the examples in an e2e test.
Expected behavior
Any examples we add to the repo should have at least a base level of testing applied to them with each PR, e.g. making sure the structure is sound (even if we don't verify the behavior).
Actual behavior
In #10 we'll be adding types and examples, but we don't yet have any tests for them.
Additional info
The text was updated successfully, but these errors were encountered: