Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epic: test coverage for content pages #52

Closed
1 of 14 tasks
ryanj opened this issue Jul 9, 2020 · 0 comments
Closed
1 of 14 tasks

Epic: test coverage for content pages #52

ryanj opened this issue Jul 9, 2020 · 0 comments
Labels

Comments

@ryanj
Copy link
Member

ryanj commented Jul 9, 2020

TODO:

v1: local content validation (BYO cluster credentials)

  • find markdown files, foreach file{
  • parse and extract example commands
  • parse example responses
  • establish test cases to ensure commands do not fail or return an error when executed in order
  • add test cases to compare example response output with actual response output, report any diffs
  • provide the date, time, and k8s API version that was most recently used to validate the content Example suited Kubernetes environment unclear #26, Example commands should be portable #63

v2: test automation

  • automated updates of example responses
  • automated test coverage (nightly)
  • report results of test runs
    • via GitHub repo
    • new /status page?

v3:

  • include separate reports per k8s release (cover last three releases of K8s)?
  • include separate reports for the two most recent releases of OpenShift?
  • investigate opportunities to contribute to, or borrow examples from upstream k8s test coverage examples
@ryanj ryanj self-assigned this Jul 9, 2020
@ryanj ryanj mentioned this issue Jul 9, 2020
5 tasks
@ryanj ryanj closed this as completed Apr 27, 2021
@ryanj ryanj added the wontfix label Apr 27, 2021
@ryanj ryanj removed their assignment Apr 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant