Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.
Unit testing revisited
- Is this about limitations of the tooling for fundamental React features, or about our approach to testing? It appears to be a little of both.
- The conversation evolved into a discussion of how we want to test components, essentially distilled to a distinction between white-box and black-box testing.
- There was some unclarity around what impact React Testing Library would have on our existing tools. @hazdiego joined the conversation, pointed to an earlier GitHub comment contrasting the solutions, and clarified that while it has feature parity to support replacing existing tools, it also comes opinionated with integration-style testing.
WordPress 5.4 Deadlines
@adamsilverstein made note that the WordPress 5.4 release is quickly approaching and that any work not addressed soon would need to be punted to a future release.
@aduth mentioned that a polyfill fix for URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org will be needed, and that he would appreciate attention on the corresponding patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. at #49360.
@gziolo mentioned a desire to improve upon this with better handling between development and production environments. He gave an example of the
wp-warning package, which should be considered unnecessary for production, since it is a noop in that environment. Due to time constraints, this is planned to be discussed further in next week’s meeting.