-
Notifications
You must be signed in to change notification settings - Fork 0
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
Closes #71: Use results file instead of API for lcps #77
Closes #71: Use results file instead of API for lcps #77
Conversation
841cb73
to
8ac81cf
Compare
Thia last commit corrects the expected results for Desktop. |
Add is_mobile is sql query Accept array for lcps
16c17d0
to
bfd38d0
Compare
Okay so,
Everything is working and passing, all green on e2e. :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.
"lcp_single_double": has no value in json. @Miraeld can you please check
@jeawhanlee thanks for the update. 2 tests failed and many has no data in database => can you please check? (I think we need to see if it's the same before the PR and while using API) |
@Mai-Saad I think I found a reason for the no result in db, since you are on e2e env, your |
* Add scenario for no lcp/atf, add plugin deactivation function #70 :closes: * fixed lint * minor fix * Add step to activate and deactivate mobile plugin * update gitignore file * PR modifications * Add new command function, pr modifications --#70 * minor modifications * Add beacon check for lcp pages * deactivate plugin, modify json * Add missing step * change steps
@jeawhanlee Should I merge it ? |
Description
Fixes #71
Documentation
User documentation
Technical documentation
This PR changes the way we are testing the result from the beacon script. In fact, before we were using Google PSI API, while now we are using a file to compare our results to the expected one.
This allow us to faster, more reliable.
Type of change
New dependencies
Risks
Checklists
Feature validation
Documentation
Code style
Observability
Risks