-
Notifications
You must be signed in to change notification settings - Fork 110
tests: add backup reminder banner test. #3666
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
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.
LGTM, with one point about not using id for tests, please change to data-testid
|
|
||
| // First, clean up cache and headers. | ||
| try { | ||
| const basePath = path.resolve(__dirname, '../../../../appfolder.dev/cache'); |
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.
Would it help to use nodejs built in process.cwd() function here instead of traversing up the directory structure?
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.
IIRC I tried but since we launch the tests from frontends/web, process.cwd() resolves to that dir. However I just slightly refactored it to be much cleaner in github CI (and moderately cleaner in non-CI :D )
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.
ah I see, no strong opinion. It was more a question.
I guess the Makefile task starts from the root, but then cd into frontends/web
Line 66 in 43b29d9
| cd ${WEBROOT} && $(MAKE) test-e2e |
|
|
||
| const { stdout } = await execAsync(cmd); | ||
| return stdout.trim(); | ||
| } |
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 engouh docker and am always confused about when to use spawn, fork or exec.
It looks very cool what you do in this file with the regtest, but I am not the right person to review this.
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.
Thanks, I will revisit this file, add some comments, and ask for another reviewer :)
fa11eee to
62f6f60
Compare
This was accidentally changed in 21ebd32
Also solves a few flakiness issues and reverts an accidental change.
Before asking for reviews, here is a check list of the most common things you might need to consider: