-
Notifications
You must be signed in to change notification settings - Fork 58
QA. Merge into trunk
#3499
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
QA. Merge into trunk
#3499
Conversation
…l-payments into qa-pay-later-messaging
Add PLM default UI test
QA - Add test `Settings - Pay Later Messaging - Disabled on all pages`
- Add test data file - Add separate subtests for each data variation - Add resulting tests according to Xray - Add helper methods to save and retreive results of subtests
Add tests for PLM configurator
* A function has been created to check and verify the console messages for badgeBoxUtils.js * Test data has been created badges-per-country.data.ts file * Test case updated to test countries included in the test data * Fix lint issues
Settings - Onboarding - Default UI test updated.
* Test for Croatia and UK removed as it is included in the first test block. * Test data for Croatia and UK removed from test data file. * Test keys updated with actual test keys from Jira
* To have a more generic approach for enabling and disabling the advanced connection options enableConnectionOptionsToggle() function created. * toggleManuallyConnect and toggleSandboxMode update accordingly.
QA- updates and fixes
…-test Qa - update visual default UI test
Some tests were removed as they are going to be automated under PCP-4318
Add test PCP-4318 Remove the tests that are in scope of PCP-4318
QA/Add test pcp 4315/4316
Some tests were removed as they are going to be automated under PCP-4318
- Update playwright-utils version in package.json - Uncomment woocommerce.setup
…l-payments into qa-fix-legacy-ui
Qa fix legacy UI
|
@Dinamiko @puntope @AlexP11223 I'm done with the changes. Readme are updated, |
|
If the site is MultiSite (the default config for project DDEV env) tests will fail. You can check this error by:
Maybe we can add in the README that the environment set in the |
|
Lots of tests are based on snapshots. But we didn't commit the snapshots. We should commit these snapshots as well. |
|
Talking about snapshots again, I'm a bit curious about Snapshot-based E2E testing. What is the rationale behind using them? |
|
|
|
Have we considered using wp-env for running the E2E tests? Here is an example how to use wp-env to run the E2E. The good thing about it is that it's ephemeral, and all the devs and also GitHub bots can even use the same standard environment for E2E tests. It's very easy to install (just a dependency) You can also load your own plugins or logic easily to manipulate the environment and connect it to WPCLI etc It's widely used in Woo ecosystem The same goes for Integration testing cc: @Dinamiko |
|
Hi, @puntope, I've disabled many visual tests and commited the screenshots for some which are more stable. There are still some failing tests but it would be nice to try running against the |
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.
Let merge as it's. I can use this as fundational and create the wp-env version from there.
Description
qabranch contains numerous updates for/tests/qadir with autotests;/tests/qa-legacy-uidir with autotests.