-
Notifications
You must be signed in to change notification settings - Fork 946
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
[frontend] e2e tests on dashbaords - chunk 2 (#6704) #7135
Conversation
471fada
to
a971fb8
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7135 +/- ##
=======================================
Coverage 67.74% 67.75%
=======================================
Files 561 561
Lines 68824 68824
Branches 5870 5872 +2
=======================================
+ Hits 46628 46633 +5
+ Misses 22196 22191 -5 ☔ View full report in Codecov by Sentry. |
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.
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.
Great PR there. Many good examples for the e2e test. Very informative 👍.
await expect(dashboardDetailsPage.getTitle(updateDashboardName)).toBeVisible(); | ||
await dashboardDetailsPage.getActionsPopover().click(); | ||
await dashboardDetailsPage.getActionButton('Update').click(); | ||
// expect(await dashboardForm.descriptionField.value()).toEqual('New description'); |
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.
Should it be kept as comments?
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.
Oh no indeed, I forgot this one thanks!
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.
Fixed
@@ -20,7 +20,7 @@ | |||
"start:cluster": "NODE_ENV=cluster node build/back.js", | |||
"serv": "node build/back.js", | |||
"insert:dev": "node build/script-insert-dataset.js --datasets=DATA-TEST-STIX2_v2,poisonivy", | |||
"insert:dev:e2e": "ELASTICSEARCH__INDEX_PREFIX=e2e node build/script-insert-dataset.js --datasets=DATA-TEST-STIX2_v2,data-test-stix-e2e", | |||
"insert:dev:e2e": "ELASTICSEARCH__INDEX_PREFIX=e2e node build/script-insert-dataset.js --datasets=DATA-TEST-STIX2_v2,data-test-stix-e2e,poisonivy", |
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.
Is the script used elsewhere? Would it be better to write the dataset directly into the script?
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.
It is the same script used for insert data for testing purpose and for local environment (cf insert:dev) that's why now we have an argument to tell which dataset to use
Proposed changes
Related issues
Checklist