Web Plugin    Run #1215

Run Properties:   Failed #1215  •  fd55ece31c ℹ️: Merge 7c027f898c10368e95f3884b44f4ab824ae4a076 into 85a6afc3498a5da21b4fbd7298dd...

Project	Web Plugin
Branch Review	press11-144-undo-excluding-tests
Run status	Failed #1215
Run duration	06m 39s
Commit	fd55ece31c ℹ️: Merge 7c027f898c10368e95f3884b44f4ab824ae4a076 into 85a6afc3498a5da21b4fbd7298dd...
Committer	Vara
View all properties for this run ↗︎

---

Test results
Failures	1
Flaky	1
Pending	1
Skipped	0
Passing	70
View all changes introduced in this branch ↗︎

Tests for review

  vendor/newfold-labs/wp-module-coming-soon/tests/cypress/integration/coming-soon.cy.js • 1 failed test

View Output Video

Test		Artifacts
Coming Soon > Has Coming Soon Section on Home		Test Replay Screenshots Video

  tests/cypress/integration/help.cy.js • 1 flaky test

View Output Video

Test		Artifacts
Help Page > Is Accessible		Test Replay Screenshots Video

The coming soon tests are skipped in this plugin because it does not contain the e-commerce module. Not ideal, but for whatever reason, e-commerce has coming-soon components in it, which change the functionality. The current tests in the coming-soon module expect the e-commerce module to be in place, but since it is not in this plugin, the plugin has its own legacy coming-soon test that is run.

Ideally, the coming-soon elements can be moved out of e-commerce and into coming soon, so it is consistent and independent of other modules, but we're not quite there yet. Once we get to that point, we should be able to do as proposed here and stop skipping the coming soon tests and remove the plugin level coming soon test too. If coming soon functionality changes so that the plugin test fails, it can be updated here at the plugin level during a release cycle.

This does seem to be causing some intermittent issues when testing the plugin though. See PRESS0-2464 for an example.