-
Notifications
You must be signed in to change notification settings - Fork 130
Add cypress tests to validate docs pages #7254
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
base: master
Are you sure you want to change the base?
Conversation
Your site preview for commit 3be2dba is ready! 🎉 http://registry--origin-pr-7254-3be2dba9.s3-website.us-west-2.amazonaws.com/registry. |
Your site preview for commit 173cb54 is ready! 🎉 http://registry--origin-pr-7254-173cb54e.s3-website.us-west-2.amazonaws.com/registry. |
173cb54
to
af5faee
Compare
Your site preview for commit af5faee is ready! 🎉 http://registry--origin-pr-7254-af5faee0.s3-website.us-west-2.amazonaws.com/registry. |
87ed893
to
babe1b0
Compare
@iwahbe - good idea! I reverted that commit locally and was able to repro. I also added an extra resource to the schema, one with the |
fixes: #6774
Adds a schema to represent a test provider that we can use to validate e2e from schema file to html rendered page is structured and contains all the elements as we expect.
If we want to go as far as rendering everything from overview page to clicking through navigation and then clicking through all the resources, then we could potentially do that, though not sure if that is necessary as what we really want to test is the pages generated contain everything we expect to guard against regressions. Though if we feel this is necessary we can follow on with that.
TODO: