The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?Create a ticket in our bug tracker.
When you conduct user testing, you are measuring to see if the feature or patchpatchA 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. accomplishes its intended purpose.
The types of user testing that WordPress needs help with are:
Setup a test site either locally or with your web hosting provider
Install the WordPress Beta TesterpluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party
With the end goal in mind, do a walk-through of the feature and take notes as you go, or record your session and take notes when you play it back. If you are testing a feature early in the design process, more open-ended suggestions and potential points of confusion are appropriate to note. If you are testing a feature later in the development process, then your main focus should be to look for blockers in the design decisions that have already been made.
One of the fastest and easiest ways to write up a task list for usability testing is to find out the feature’s end goal and then do a walk-through yourself. Take notes as you go through each step, or record the walk-through and then write down the steps when you play back the video. This will also help you set an expectation for how long the test may take others.
If you use any assistive technologies, such as JAWS or any other screen reading software, testing using those would be a great addition to user testing.
Start with a specific scenario. These are imaginary situations that help people get into the right mindset for completing a task. Feel free to have fun with it! Choose a scenario that mimics the real world as much as possible, so that people can engage with the tasks as if they are real. Here is an example:
You’re setting up a website for a new department. You need to set some people up so they can add content, and others will need to be able to submit content that must be reviewed before it can be published.
Tasks should be realistic and clearly written without describing the steps in too much detail. Use language you think would be used by users, and avoid giving clues like specific words used on the site. You’ll also want to avoid asking people what they “think,” because you want to focus on what they actually do and not what they think they might do.
Goal: Look up a user role.
Poor task: You want to see the role for your co-worker. Go to the website, sign in, and tell me where you would click to find user roles.
Better task: Look up the rights for your co-worker, Sally, to make sure she is able to publish new content.
Choose a location where you are likely to find your target audience. WordPress meetupMeetupAll local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. groups are a great resource. Another potential source of volunteer testers is your local WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more., where people can sign up to help test during breaks—ask your local WordCamp organizers if they have space for a breakout area for user testing. Some people also find testers at coffee shops.
It is common to compensate users for their time, though many WordPress contributors will volunteer their time if you ask up front. At meetup groups, buying food like snacks or pizza for the group can be a good incentive for adding some time to the meetup for testing. When testing, don’t underestimate the power of chocolate, or offering to cover the cost of a cup of coffee in exchange for a few minutes of their time. Giving a small gift card is reasonable for a short test. Longer tests should be paid. If you don’t have a budget for testing, consider asking your local WordPress group if they might be able to work with you to raise money for user research.
When conducting a test, encourage users to think out loud and either record their onscreen interactions with a tool such as QuickTime or take notes during the test. Try not to be leading or answer questions. Just pay close attention to what they do onscreen as they think aloud and find their way through the tasks. Your goal should be to take out as much bias as possible and pay attention to what you can observe someone doing.
Whether you are reporting results from a walkthrough or from a test with another user, the most valuable results you can report are bugs that blockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. you from completing the goal or trends about pain points and satisfaction rates. A short “Top 5” list of bugs and pain points should be at the top of any report followed by notes, personal suggestions (labeled personal as they may have bias), and details of the test.
If you recorded a video, it’s helpful to include a link to it in your report or a highlight reel if you have tested with several people.