You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 1, 2020. It is now read-only.
I need to check if my changes to core affect output in an unexpected way. I also need to make sure my changes meet the needs of spec.
We have no good way to ensure that Node and PHP are developing towards spec or if we are in compliance. We use the demo but it doesn't address all of the various test cases we need to develop to properly define the boundaries of the spec.
An Acid Test StarterKit could give us a common base to use for testing. If we roll in visual regression testing we can quickly see where our changes break the expected output. This idea is based on the initial work of James Nash so full credit to him for the idea.
The timeline for this feature is sooner rather than later. At a minimum we can roll out the StarterKit and tack on visual regression testing at some point in the future. I'm willing to put together the patterns for the StarterKit as PHP is closest to being spec-compliant.
Tagging process-enhancement because this is all about making sure we work better together across platforms.
This vote will close at 10EST on July 22nd or once two voting members have given the yay or nay.