The Test team patrols, curates, and tests the WordPress experience. We use a QA mindset to do visual records, using, observing, user research, manual testing, and user testing. We also document and triage top flows.
Page on front settings
Page revisions
Post revisions
Call for testing: Gutenberg
Gutenberg is now in beta, with that comes a new opportunity for testing.
There is now a testing page dedicated to Gutenberg, you can find it right here. There are currently 2 types of testing being looked for, each has a central feedback form.
Looking for other ways to give feedback? You can also write a blog post (let the editor team know about that in Slack #core-editor) or add an issue to the GitHub repository.
Your feedback and testing is really important at this stage of Gutenberg, it really does matter and help make this as good as it can be.
Additional CSS
Step one: click additional CSS
Step two: add CSS
Step three: save
Theme editing
Step one: click edit
Step twor: see edit screen
Step three: click in see underlines
Step four: save edit
Step rive: change files
Step six: switch themes
Step seven: theme loads
Plugin editing
Step one: click edit
Step two: edit screen
Step three: click into textarea get underlines
Step four: look up function
Step five: new tab see function details
Step six: save change
A new call for testing…
A new call for testing is out for the prototype editor. It looks neat! If you’d like to help test, remember that it’s in very early prototype stages so functionality is limited and they’ve asked for help with the following (other functions haven’t been built yet):
- Add a new paragraph.
- Add an image.
Written response:
- Is it clear what each section does?
- How do the flows for adding paragraphs and images feel overall?
Post testing notes on the thread at https://make.wordpress.org/design/2017/02/09/initial-gutenberg-prototype-editor-testing/
Report bugs (search first!) at https://github.com/WordPress/gutenberg/issues
