-
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
🐛(tests) more stable tests #22
base: main
Are you sure you want to change the base?
Conversation
When bootstraping this project in the dev branch two additional directories are created: edx/src and edx/modules. To ease switching between a feature branch and the dev branch we choose to ignore the edx/modules directory.
When bootstraping this project in the dev branch two additional directories are created: edx/src and edx/modules. To ease switching between a feature branch and the dev branch we choose to make the linter ignore the edx directory.
To keep the circleci machine up to date.
9a6430f
to
0f034f4
Compare
command: make bootstrap run-edx | ||
- run: | ||
name: Run e2e tests | ||
command: make run-edx test | ||
command: make test |
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 don't understand why you changed the commands
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.
The idea was to group together similar tasks.
Currently, in the bootstrap ci step, we start all services except the edX CMS and then in the test step, we start the CMS and run the tests.
Thus, I suggest starting all services in the bootstrap CI step and only running the tests in the test CI step.
WDYT?
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.
Indeed I think it's a good idea 👍
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.
See #23 comments. Sorry for mixing up reviews.
93a9f6e
to
d152577
Compare
The iframe in the js_input_response test needs some time to become interactive. Therefore we disable chromeWebSecurity to give cypress access to the cross-domain iframe to check whether the iframe is ready or not.
The drag_and_drop test relies on the problem beeing at it's initial state. However, edX preserves the state of the problem once it's submitted. Therefore we reset the drag_and_drop problem before answering it.
d152577
to
152a6e9
Compare
Purpose
The
js_input_response_spec.js
test occasionally fails when it tries to access an iframe that has not yet been properly initialized.The
drag_and_drop_spec.js
test always fails on a second run because it preserves its previous state.We also updated the circle ci machine image to stay up to date and added entries to
.gitignore
and.eslintignore
to ease switching between the dev and feature branches.Proposal
js_input_response_spec.js
- wait for the iframe to initializedrag_and_drop_spec.js
- reset the problem before each attempt