-
Notifications
You must be signed in to change notification settings - Fork 1
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
test(e2e): onboarding tests #162
Conversation
269a5cd
to
aa7d5f2
Compare
8c5fb69
to
adfd2d2
Compare
304e9c9
to
bec020b
Compare
bec020b
to
ba33585
Compare
Signed-off-by: Zacharias Fragkiadakis <zacfragkiadakis@gmail.com>
- Refactors some tests in onboarding.spec.ts using `browser.waitUntil` to reduce flakiness - These assertions will now poll for the result instead of failing immediately - Simulates Radicle installation in the onboarding process by renaming the node home directory - Extracts common queries, actions, and assertions to helper files Signed-off-by: Zacharias Fragkiadakis <zacfragkiadakis@gmail.com>
Signed-off-by: Zacharias Fragkiadakis <zacfragkiadakis@gmail.com>
983019b
to
adf2a6d
Compare
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.
Please let me know if the single comment-assumption I've made is inaccurate and I'll insta-approve.
In general, and from a reader's perspective, I like how the testing architecture is shaping up, well done!
Naturally, I'll be able to form a more thorough verdict after I write a few tests of my own.
- Uses wdio's `onWorkerStart` hook to move the radicle directory before launching vscode - This is only done on the onboarding suite worker Signed-off-by: Zacharias Fragkiadakis <zacfragkiadakis@gmail.com>
9142baf
to
cf74866
Compare
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.
Well done, zac, and thank you!
Prerequisite #169
Closes #163
.radicle
from it's default locationbrowser.pause
(used on some flaky tests) in favour of usingbrowser.waitUntil
(asynchronous assertions). This should reduce overall flakiness when adding new tests to the suite.