Theme test results added to Trac tickets

Starting today, a subset of Themes Trac tickets may include an automated reply showing the results of end-to-end theme tests. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. tickets already include Theme Check results; the new automated e2e testing covers extra tests intended to find JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. errors, invalid output, potential a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( problems, and other items from the Guidelines.

The Theme Test results are intended to help both theme reviewers and theme authors discover theme bugs and potential problems easier and earlier. It is a work in progress that we hope will assist and augment the manual review process for themes. The tests are advisory only, there is no requirement or expectation that themes must pass the tests in order to be approved. Here’s an example:

We’d like to hear your feedback on the tests, and suggestions for additions and improvements. You can discuss those in comments here or post issues to the Theme Review Action repository in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner.


cc +themes

At the theme review team we’d would like…

At the theme review team we’d would like to increase the automation of our processes and try and make things a little easier for new members to become reviewers. In light of this we have a tool request for a new reviewer assignment button.

Spec of an assignment button:
A button that when clicked takes the The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. username logged in as and assigns the next ticket in the #4 queue. This will only ever assign one theme, if you have one not approved but in review you can’t get another this way – you must do one by one. It will also cc in any admins we want – primarily thinking Emil and me.

Placement of button and extras:
Along with this, there would be a report we could look at that showed any of these themes. This button will live as a menu item and also on the handbook in the ‘How to Join’. This will remove the request post requirement forever. This post creation each season is a bit of a pain point and people ask a lot where it is, this will solve that. It will also mean at contribution days people can get a theme without an admin being around. That should have a knock on effect of increasing reviewers – which is great.

As far as the term button goes, this could be a link to a page. The idea is though it is obvious. Perhaps button styling would achieve this, but we’re flexible about that. The goal is it’s obvious though and easy to use.

Any questions I’d be happy to answer.