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. A test plan is being developed with lists of things to check out, which we will be posting here shortly. If you have any questions, email okeyes@wikimedia.org.

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:


 * Feedback page: This bare bones version is for internal tracking only, wait to test this feature until a full feedback page is ready.
 * Feedback page: This bare bones version is for internal tracking only, wait to test this feature until a full feedback page is ready.


 * Option 4: Call to Edit


 * Option 5: Current AFT v4


 * Option 0: No feedback form

See also:
 * Technical test plan
 * Feature requirements page
 * How to reporta bug (below)
 * Detailed testing instructions (see below)

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': https://bugzilla.wikimedia.org/enter_bug.cgi

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

5. Component:
 * Enter 'ArticleFeedbackv5' (that's the new version)
 * Do *not* enter 'ArticleFeedback' (that's the old version)

6. Version:
 * Select 'any'

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

8. Hardware:
 * Select one of these tags to identify the computer you are using: All, HP, Mac, PC, Other

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

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

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

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

12. Attachment:
 * Include a screenshot (if it helps show your bug visually).

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 one of these keywords to identify which phase of this project is impacted by your bug:
 * aftv5-1.0 - Phase 1.0 bug (Dec. 12 launch)
 * aftv5-1.5 - Phase 1.5 bug (Dec. 21 launch)
 * aftv5-2.0 - Phase 2.0 bug (Jan.-Feb. 2012 launch)
 * If you are not sure, enter aftv5-1.0 so it's visible to us, and we will sort it for you.
 * To learn more about phases for this project, check our [ feature requirements page].

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

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

https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=aftv5-1.0&list_id=61530
 * To see all of the bugs that are now being worked on for phase 1.0, check this Bugzilla search page:

Other ways to report bugs
If you're not comfortable using bugzilla, bugs can also be posted in the "known issues" section of this page, or sent to improve@wikimedia.org. Please include precise details, including what browser (and what version) you are using.

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: https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=aftv5-1.0&list_id=61781

Overview
Here is an edited log of the IRC chat session we held on Wikimedia's Office Hours on Dec. 8, led by Fabrice Florin: IRC office hours/Office hours 2011-12-08.

Edit CTA Logic
We want to test the AFTv5 Edit CTA logic, and to make sure that the AFTv5 Call to Edit is only shown if users have the right to edit a page.

To that end, we have created the following two test pages, and asked for someone with Admin privileges on prototype to semi-protect and fully protect them for testing purposes:

Semi-protected page test: http://prototype.wikimedia.org/release-en/Edit_semi_protected_page_test

Fully protected page test: http://prototype.wikimedia.org/release-en/Edit_protected_page_test

Note that these test pages are now editable and this test cannot begin until we either have admin privileges to do this ourselves -- or an administrator for prototype is kind enough to protect and semi-protect these pages for testing purposes.

We will then ask regular users (without admin or edit privileges) to test whether or not the Edit CTA is shown on these protected or semi-protected pages. We will also ask them to confirm that they cannot edit this page through other means.

You can read more about this Call to Edit on our AFTv5 feature requirements page: http://www.mediawiki.org/wiki/Article_feedback/Version_5/Feature_Requirements#Edit_this_page