-
Notifications
You must be signed in to change notification settings - Fork 2
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
Common components integration tests #82
Conversation
Codecov Report
@@ Coverage Diff @@
## main #82 +/- ##
===========================================
+ Coverage 29.94% 40.11% +10.17%
===========================================
Files 12 12
Lines 688 688
===========================================
+ Hits 206 276 +70
+ Misses 482 412 -70
... and 4 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🍉🍉
I like this very much, and it runs.
hi @samcunliffe, re-requesting a (hopefully quick) review for the parametrised tests. also tagging @niksirbi since he has experience with fixtures inside parametrize input arguments (thanks!) Ideally I would like to have one fixture with the page name and title of all pages but didn't find a way around it... 🤔 |
Co-authored-by: Sam Cunliffe <[email protected]>
Co-authored-by: Sam Cunliffe <[email protected]>
So it was an XPASS and we had XFAIL strict (expected fail, but found the test to pass therefore FAIL). Without strict we get an XPASS on Windows. Something to investigate further as we add more tests.
Integration tests to check if the components common to all pages are created. The common components are the page content container and the sidebar.
For the sidebar, we also check that clicking each link takes you to a page with the expected title.
Right now, if no config file is loaded in the Home tab, each of the subsequent pages will return an error in the browser console (see issue #81). I wrote a test for that and marked it with
xfail
(expected fail) for nowCloses #27