Style Engine: move PHP unit tests to Gutenberg

[ramonjd]

WAS?

Greetings humans!

This PR moves style engine PHP unit tests to Gutenberg /phpunit directory and adds 'Gutenberg' and 'gutenberg' prefixes/suffixes.

I thought about adding a build step to copy/search/replace the tests, thereby keeping the PHP unit tests in the package folder, but decided against it because:

• adding more steps to the watch task might slow it down
• rebuilding unit tests in order to run them would probably be annoying
• new features are specific to the Gutenberg plugin anyway

WARUM?

After 6.1, the style engine classes and methods are in Core.

Moving the tests and using the Gutenberg functions and classes allows us to continue development and avoid class collisions.

This PR also proposes to add a bash script to make Core backporting more easy.

The script and .gitignore files are optional and are only there to spark discussion. I'm thinking we shouldn't commit them.

WIE?

Manually relocating files and adding _Gutenberg class and gutenberg_ function suffixes/prefixes.

Testing Instructions

Lint and run all the tests!!

npm run test:php 

Or run a single test using the test class name!!

Example:

npm run test:unit -- --filter WP_Style_Engine_Test
npm run test:unit -- --filter WP_Style_Engine_CSS_Rules_Store_Test

[ramonjd]

I reckon we don't really need something like this. I'll remove it in a future commit.

Doing it via IDE is just as fast and means less work.

I just wanted to make sure we don't need to worry that the PHP unit tests no longer live in the package file.

The Core tests exist as well so I think we're covered.

[andrewserong]

I kinda love the idea of including bash scripts somewhere to make this process a little easier. But yes, maybe in another PR? There could potentially be a good home for it in /bin/ somewhere?

[andrewserong]

Thanks for the updates here! Just gave this is a quick test, the tests are passing for me, looks like you captured all the wp → gutenberg conversions, and the removal of the packages test suite appears to be safe since it was only used by the style engine package.

LGTM!