Skip to content

Conversation

@mishautkin
Copy link
Collaborator

Description

qa branch contains numerous updates for

  • automated env setup scripts;
  • /tests/qa dir with autotests;
  • /tests/qa-legacy-ui dir with autotests.

mishautkin and others added 30 commits March 6, 2025 19:18
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
* 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.
* Test cases in serial block reordered.
* Some steps added to the test cases to prevent failure.
…-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
Some tests were removed as they are going to be automated under PCP-4318
@mishautkin
Copy link
Collaborator Author

mishautkin commented Sep 4, 2025

@Dinamiko @puntope @AlexP11223 I'm done with the changes. Readme are updated, .zip files are there now. The scripts work on my side. Could you please review and try out the scripts?

@puntope
Copy link
Collaborator

puntope commented Sep 5, 2025

If the site is MultiSite (the default config for project DDEV env) tests will fail.
Also if I deactivate the multisite in my environment and perform the test against the environment created by the repo the foundation tests fails.

You can check this error by:

  • cloning the repo (using this branch)
  • npm run ddev:setup
  • Remove lines in .ddev/wordpress/wp-config.php regarding multisite
  • cd tests/qa
  • npm run setup:tests
  • npm run all

Maybe we can add in the README that the environment set in the .env should not be a fresh WordPress Single site and not the one created using ddev:setup

@puntope
Copy link
Collaborator

puntope commented Sep 5, 2025

Lots of tests are based on snapshots. But we didn't commit the snapshots. We should commit these snapshots as well.

@puntope
Copy link
Collaborator

puntope commented Sep 5, 2025

Talking about snapshots again, I'm a bit curious about Snapshot-based E2E testing. What is the rationale behind using them?

@puntope
Copy link
Collaborator

puntope commented Sep 5, 2025

03-Plugin Settings Tests are timing out for me. If they work for you, maybe is something not correctly setup in my env?

@puntope
Copy link
Collaborator

puntope commented Sep 5, 2025

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

@mishautkin mishautkin changed the base branch from trunk to develop September 8, 2025 13:06
@mishautkin
Copy link
Collaborator Author

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 wp-env or Kinsta, since our current SSEs are a bit slow and may cause problems by themselves.

Copy link
Collaborator

@puntope puntope left a 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.

@Dinamiko Dinamiko merged commit da009ae into develop Sep 17, 2025
7 checks passed
@Dinamiko Dinamiko deleted the qa branch September 17, 2025 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants