Opened 2 years ago
Closed 2 years ago
#60402 closed enhancement (worksforme)
Testing: Add an e2e tests that checks Gutenberg + WordPress trunk
| Reported by: | youknowriad | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Build/Test Tools | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
On several occasions when merging Gutenberg changes into Core, we noticed PHP fatal errors due, in most cases, to duplicate class names.
To prevent this from happening again, we added lint rules to Gutenberg to force developers to check existence of classes before defining them.
That said, this is not sufficient and won't catch all incompatibilities and to help us catch these sooner and prevent failures for people using both Gutenberg and WordPress, we should consider adding a basic e2e test to Core that installs Gutenberg trunk (or latest Gutenberg version) and check that the frontend and backend are not broken (load without fatals).
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I actually just realized that a test like this is already in place in Core. The problem is that it didn't catch the previous error due to it being php version specific.