Article feedback/Version 5/Testing

Welcome to our testing page for the Article Feedback Tool Version 5 (AFT V5)!

Thanks for helping us test the beta version of this new feature. Here are instructions on how you can contribute during phases 1.0 and 1.5 of this project in December 2011. You can also make suggestions in the talk page, as well as a file bugs in Bugzilla URL.

See also: project overview page, feature requirements page, interactive prototype, as well as technical design page, data and metrics plan.

Overview
We're looking for a few volunteers to help us test beta software for phase 1.0 of AFTv5. No special technical skills are required, though participants need to be methodical in their reporting. Of course, we would love contributors who already have some experience in software testing.

If you would like to give us a hand, please sign up your name below and email community liaison Oliver Keyes: okeyes-at-wikimedia-dot-org.

Team Sign-up
Please add your Wikipedia user name here to join our testing team for AFTv5, so we can stay in touch. Thanks!

How to post on Bugzilla
If you encounter a technical bug or serious issue, follow these steps to post it on Bugzilla:

1. Go to Bugzilla on Wikimedia: https://bugzilla.wikimedia.org/

2. Log in ( or create a new account)

3. Enter a bug Click on enter a new bug (If your bug hasn't been reported yet): https://bugzilla.wikimedia.org/enter_bug.cgi

4. Click on 'MediaWiki extensions'  (our product type)

5. Component:
 * Enter 'ArticleFeedbackv5'
 * Do *not* enter 'ArticleFeedback'

6. Version:
 * Select 'any' for now
 * (coming soon) Select '1.0' for phase 1.0 features (or '1.5' for phase 1.5 features)

7. Severity: blocker, critical, major, normal, minor, trivial, enhancement.
 * Select one of these tags:

8. Hardware:
 * Select one of these tags: All, HP, Mac, PC, Other

9. OS:
 * Select the operating system used by your computer.

10. Summary:
 * Enter a headline for your bug, that describes the problem in one line

Tip:
 * Bugzilla automatically searches to see if your bug has already been reported.
 * If your bug has already been reported, do not submit a new bug

11: Description:
 * Describe what happened, in detail.
 * What steps can we take to reproduce this bug?
 * What did you expect should have happened?

12. Attachment:
 * Include a screenshot if appropriate.

13. Submit your bug: Click 'Submit Bug' button at the bottom of the page

14. URL:
 * Add a URL for the page where your bug can be found

15. Keywords:
 * Add any keywords that would help find out what this issue is about (e.g.: option 1, feature request)

16. Web Browser: (e.g. Google Chrome, Mozilla Firefox 4.x - see list of supported browsers)
 * Include your browser name and version

17. Save changes: Click 'Save changes' to save this additional information.

Phase 1.0
Here are links to the key 1.0 modules we would like you to test first:


 * Option 1: Did you find what you were looking for?


 * Option 2: Share a suggestion, question, problem or praise


 * Option 3: Review this article

There is no direct link for this CTA. You have to complete one of the three feedback forms to see it. Please take the time to test that key deliverable.
 * Call to Action: Edit this page

Phase 1.5
Here are links to the key 1.5 modules we will want to test the following week:


 * Option 4: Call to Edit


 * Option 5: Current AFT v4


 * Option 0: No feedback form


 * http://prototype.wikimedia.org/release-en/Special:ArticleFeedbackv5/Test_table Feedback page] (bare-bones, for internal tracking only, no need to test now)

What to look for
OmniTI is now preparing a test plan with lists of things to check out, which we will be listing here shortly.

Other ways to contribute
There's lots of great ways for you to help us improve the Article Feedback Tool. Besides posting bug reports on Bugzilla, we also welcome general suggestions on this talk page. And we encourage you to get more informed about this project, to save time.

Make a suggestion
To share a comment or idea about this new feedback tool, follow these easy steps:
 * Go to our talk page for testers (click 'Discussion' above)
 * Find the feature that you would like to comment on
 * Add your comment in the appropriate section

Get informed
To save time, check out these two important references:
 * Scan the feature requirements page to see what the software is expected to do.
 * Read the list of known issues below to see if your issue has already been reported

Known issues
Here are some of the bugs, glitches and problems we already know about. If your issue matches one of these, you do not need to report it at this time:

Phase 1.0
These features are scheduled for 1.0 and need to be tested first. Here are known issues for 1.0.

You are welcome to add new issues if you find some, but please follow the format below for consistency, and be sure to sign and date each of your posts, so we know who it came from.

Overall

 * Bold title: 'Help improve this article'
 * Let's bold the font for the form titles to make them stand out more. -- Fabrice Florin 01:06, 6 December 2011 (UTC)
 * See Bugzilla bug: https://bugzilla.wikimedia.org/show_bug.cgi?id=32818


 * Text fonts in comment boxes
 * On Firefox, the text fonts should be sans-serif (instead of serif) and should be larger: 1.1 em / 13 pt (for both gray text prompts -- and for actual user comments) -- Fabrice Florin 07:53, 3 December 2011 (UTC)


 * Legal text
 * Let's move the small legal text right right below the text box and above the 'Post your feedback' button, left-aligned ("By posting, you agree to transparency under these terms.") This will insert an extra line and increase the height of the form by 30 pixels or so. But that's the placement that Brandon recommends -- and it will make it easier for us to add on that line a link to the feedback page (when we are ready to make it public). -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * Change its font color to the same shade of gray as the text prompts (instead of pure black) -- (see new mockup below). -- Fabrice Florin 07:53, 3 December 2011 (UTC)


 * 'Post your feedback' button
 * Add more space around 'Post your feedback' button, a couple pixels both above and below, so there's a bit more breathing room (see new mockup below) -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * Sometimes my first click on 'Post your feedback' does nothing -- and I have to click a second time to post my feedback. Can you reproduce on your end? -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * Consider having a message if they click on the grayed-out 'Post your feedback' button. Something like: 'Please share more feedback.'  -- Fabrice Florin 07:53, 3 December 2011 (UTC)


 * Style guide consistency
 * Are the buttons consistent with the style guide? We're using a mix of shadows and no-shadows. -- HowieF 12-05 12:26am PT

Option 1
Did you find what you were looking for? http://prototype.wikimedia.org/release-en/Test_table?bucket=1


 * Copy tweaks
 * See if we can tighten up the copy for "Help Improve This Page/Did you find what you're looking for?" (option 1) -- HowieF 12-05 12:26am PT


 * Acknowledge previous posts
 * Once a user submits a rating/comment and reload the page, the page doesn't acknowledge the fact that the user just submitted. This may be okay for the test phases, but we should think more carefully about what we want the interaction to be.  We should at least acknowledge the user submitted the rating so the user doesn't think the feature is broken. -- HowieF 12-05 12:26am PT


 * Yes/No buttons ** When the mouse hovers over 'Yes' or 'No' buttons, show a blue highlight (instead of gray). ** Clicking on 'Yes' or 'No' on Firefox inserts a text cursor between the letters. This should not happen. (thanks for fixing this on Chrome and Safari). -- Fabrice Florin 07:53, 3 December 2011 (UTC)

Option 2
Share a suggestion, question, problem or praise http://prototype.wikimedia.org/release-en/Test_table?bucket=2




 * Tabs
 * Let's use a larger font for the tab labels (Suggestion, Question, Problem and Praise), increasing them by a couple points, to about 1.3 em or 15 points (as shown in this new mockup, also attached)  -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * The four tabs should be more spaced out apart from each other, rather than being all squished together on the left (see new mockup)  -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * The first tab is selected by default ('Suggestion'), with a cartoon bubble around it. (the other tabs are unselected, without any border around them)  -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * This version of the form is inspired by the design of getsatisfaction.com, which can provide more info. -- Fabrice Florin 07:53, 3 December 2011 (UTC)


 * Icons
 * We are now displaying all four icons in color from the start, so people are more inclined to click on them. Will discuss all icons issues with Brandon on Monday.
 * The light bulb icon is still hard to read, and needs a bit more of an outline around the edges, maybe increase the black levels and color saturation (see new mockup).
 * The heart icon is using a really bright red color that detracts from the other icons. Let's decrease its color saturation (-40) and increase its lightness (+16). -- Fabrice Florin 07:53, 3 December 2011 (UTC)

Option 3
Review this article. http://prototype.wikimedia.org/release-en/Test_table?bucket=3


 * Copy tweaks
 * See if we can use text that's a little less dull for the tooltips underneath the stars -- HowieF 12-05 12:26am PT


 * Subtitle
 * In the subtitle, let's say 'Is this article helpful?' (instead of 'How would you rate it, overall?')  -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * For the labels that appear below the rating stars, use these new words: 1=not helpful at all, 2=not very helpful, 3=average, 4= helpful, 5=very helpful (instead of 'bad => good') -- Fabrice Florin 07:53, 3 December 2011 (UTC)


 * Icons
 * On Safari, the little trash icon appears below the stars when the page is first loaded, as well as when I select a star. -- Fabrice Florin 07:53, 3 December 2011 (UTC)

Call to Action 1
Edit this page There is no direct link for this CTA. You have to complete one of the three feedback forms to see it. Please take the time to test that key deliverable.


 * Remove the title
 * Let's remove the 'Help improve this article' from this CTA. This title should not appear in any call to action.  -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * In place of this title, the confirmation message should appear at the top of the form (Thanks! Your feedback has been saved.) -- Fabrice Florin 07:53, 3 December 2011 (UTC)


 * Subtitle wraps around
 * On Firefox, the subtitle wraps around to an extra line ('Did you know that you can edit this page?'). Please extend the length of this field to avoid this. -- Fabrice Florin 07:53, 3 December 2011 (UTC)


 * New link for 'Learn how to edit'
 * 'Learn how to edit' links should take you to the Wikipedia tutorial: http://en.wikipedia.org/wiki/Wikipedia:Tutorial -- Fabrice Florin 07:53, 3 December 2011 (UTC)


 * Help tool tip
 * When I click on the Help (?) question mark icon wile the call to action is in overlay mode, I cannot click on the 'X' close box or the 'Learn to edit' links. They should both work in that mode as well. -- Fabrice Florin 07:53, 3 December 2011 (UTC)

Feedback Link
The feedback link for phase 1.0 is below the article title bar (Option B in our feature requirements). Clicking on it shows the feedback form as a modal overlay with a gray page background. Please take the time to test that key deliverable.


 * Feedback label
 * The current feedback label at the top right is not very noticeable (particularly when the fundraiser is going on.) -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * It also doesn't match what we are saying at the top of the form ('Help improve this page') -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * Consider replacing the word 'feedback' with 'Help improve this page >>', to make it more visible and consistent. -- Fabrice Florin 07:53, 3 December 2011 (UTC)


 * Feedback links should still be available after you post
 * After clicking the 'Post your feedback' button, the [feedback] link should not disappear, so I can post more feedback if I want. -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * Right now, nothing happens when I click on [feedback] link when looking at the 'Call to edit' CTA. -- Fabrice Florin 07:53, 3 December 2011 (UTC)

Phase 1.5
These issues are for phase 1.5 features scheduled for launch on Dec. 21. They are less important to test this week than phase 1.0 issues.

Feedback page
Bare-bones page, for internal tracking only, no need to test for now. http://prototype.wikimedia.org/release-en/Special:ArticleFeedbackv5/Test_table

Feedback page tweaks for 1.0:
 * Once you are caught up with top-priority issues above, please consider these minor tweaks:
 * Can we show more posts on a page, so we don't have to keep clicking More? How about showing 25 posts at a time? (instead of only 5 now) -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * Let's have the 'More' text link show all posts to date, rather than just 5 more (we could rename it 'Show all', if you like) -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * Can we put 'Hide this' and 'Flag as abuse' on the same line for now, with a vertical '|' divider between them, so they take up less space? -- Fabrice Florin 07:53, 3 December 2011 (UTC)
 * Can we also add at the start of that same line what form option was used for this post? ('option 1', 'option 2', or 'option 3', followed by a a vertical '|' divider ), as so: 'Option 3 | Hide this  |  Flag as abuse' -- Fabrice Florin 07:53, 3 December 2011 (UTC)

Option 4
Call to Edit http://prototype.wikimedia.org/release-en/Test_table?bucket=4

No comments so far.

Option 5
Current AFT v4 http://prototype.wikimedia.org/release-en/Test_table?bucket=5

No comments so far.

Option 0
No feedback form http://prototype.wikimedia.org/release-en/Test_table?bucket=0

No comments so far.