Research and document testing process

[kittenkamala]

While some documentation exists on the current test process, of course this documentation can be iterated on and improved as part of streamlining the release cycle.

[kittenkamala]

https://make.wordpress.org/core/handbook/testing/
https://github.com/sebastianbergmann/phpunit
https://make.wordpress.org/core/handbook/testing/automated-testing/qunit/
https://github.com/WordPress/phpunit-test-runner
https://github.com/WordPress/phpunit-test-reporter

[kittenkamala]

I previously put this comment in the wrong issue - should have been in this one.

MaryBaum pointed out there are multiple areas for testing involved.

test scripts used to mimic user activity - https://make.wordpress.org/test/
phpunit test runner and report used for hosts to test with -
https://github.com/WordPress/phpunit-test-runner
https://github.com/WordPress/phpunit-test-reporter/
Individual tests that core developers write when a patch is made

[kittenkamala]

One way testing can be improved to support a more streamlined development process:

• update the test runner and reporter to collect more types of metrics and to allow hosts to be able to submit multiple reports from the same user. This means more information coming in about potential global issues as hosts test out new releases. The hosting team has already started this process.

[kittenkamala]

Hristo is prepared to work on improving E2E testing
https://github.com/WordPress/wordpress-develop/tree/master/tests/e2e https://github.com/WordPress/gutenberg/tree/master/packages/e2e-tests