Recent changes to Mod Feedback

WikiPage Mod Feedback modified by JustJ

JustJ — Wed, 30 Jan 2013 16:38:48 -0000

--- v9
+++ v10
@@ -1,7 +1,7 @@
 All items are required in requesting help, feedback, or reporting a problem.  Failure to do so will result in your ticket being closed as invalid.  YOU HAVE BEEN WARNED. :-)

 1. Download the addon [here](https://sourceforge.net/p/whatsyourdamage/files).
-* Check the main [wiki:Home] page for updates on your class/spec.  If an issue is listed there as NOT fixed (or your class/spec hasn't been started yet), do not file a report, we know this already.  If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
+* Check the main [wiki:Home] page and [Known Issues] for updates on your class/spec.  If an issue is listed there as NOT fixed (or your class/spec hasn't been started yet), do not file a report, we know this already.  If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
 * Check the [tickets](https://sourceforge.net/p/whatsyourdamage/tickets) open and see if an issue was already reported. DO NOT REPORT THE SAME ISSUE as someone else.  Nobody wants to see 50 tickets saying the same thing.  Yours will be closed as a duplicate and ignored otherwise
 * Open a new [ticket](https://sourceforge.net/p/whatsyourdamage/tickets) using the following criteria:
     - **REQUIRED**: Subject should be short but descriptive.  Example:  "LUA error upon login for (class - spec)"

WikiPage Mod Feedback modified by JustJ

JustJ — Wed, 30 Jan 2013 16:37:35 -0000

--- v8
+++ v9
@@ -17,14 +17,14 @@
         * **REQUIRED**: Write down your in-combat stats as you use an ability (screenshots are fine) (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
         * **REQUIRED**: Any procs active at the time of the issue (set bonuses, trinket procs, ability procs, etc.)
         * **REQUIRED**: Write down the numbers listed in combat for said ability you think is wrong
-        * **REQUIRED**: Write down any buffs you had (that may not be listed or explicitly stated in your above numbers) during and BEFORE combat
+        * **REQUIRED**: Write down any buffs you had (that may not be listed or explicitly stated in your above numbers) during and BEFORE combat. **EXTREMELY HELPFUL**: Include the spellids of the buffs as they appear in your BUFFs area (not your action bar).
         * **REQUIRED**: Write down any tier bonuses, trinkets, etc, you have.  
         * **OPTIONAL**: You may also include a link to your character in the armory if it will help us figure out what's going on - but make sure you are in the gear and spec on the armory for the one you are reporting.  
         * **OPTIONAL**: World of Logs link to testing on a combat dummy are completely fine and probably cool enough to help troubleshoot.
     - Add any relevant attachments in the ticket, but please understand that they should be in universally usable format (screenshots in jpg, png, gif, bmp format are fine), text captures in TEXT format are fine (**DO NOT SEND WORD DOCUMENTS**, Thanks).
     - **NOTE**: Do not add opinions on tickets. State the facts and report what you are 'expecting' or 'unexpectedly' received.
-    - **NOTE**: Avoid long winded arguments (nobody wants to read it, I certainly don't either)
+    - **NOTE**: Avoid long winded arguments (nobody wants to read it, we certainly don't either)
     - **NOTE**: Do not ask unrelated questions to the issue at hand
     - **NOTE**: Do not post in someone else's ticket to say "me too" (and anything like that) or chime in unless you can offer a fix or otherwise contribute to troubleshooting the problem.
     - **NOTE**: Do not bump tickets to ask for an update. You'll get an update when project members can provide one.
-* **NOTE**: Do NOT pester any project member in game for support.  All support is done through this site ONLY.  (Trust me, nobody contributing to this will be able to answer an unending stream of questions.  You're not the only one using this mod, so consider that.)
+* **NOTE**: Do NOT pester any project member in game for support.  All support is done through this site ONLY.  (Trust us, nobody contributing to this will be able to answer an unending stream of questions.  You're not the only one using this mod, so consider that.)

WikiPage Mod Feedback modified by JustJ

JustJ — Fri, 18 Jan 2013 01:04:43 -0000

--- v7
+++ v8
@@ -1,27 +1,30 @@
 All items are required in requesting help, feedback, or reporting a problem.  Failure to do so will result in your ticket being closed as invalid.  YOU HAVE BEEN WARNED. :-)

 1. Download the addon [here](https://sourceforge.net/p/whatsyourdamage/files).
-* TICKET REQUIRED INFO:  Note your version number AND type - this is highly important.  Types are listed here:
-    -    Alpha: This code type is unstable and bound to have problems.  If you do not want to test potentially unstable, unfinished, or otherwise experimental code, do not use this.  Generally, only a small number of people should want to test this (usually a developer or a closed set of alpha testers).
-    -    Beta:  This code type is generally thought to be stable but may have a few lingering problems. Generally, more people will want to test this and will not be surprised if there are errors.
-    -    Release:    This code type is stable.  While it may have some unexpected errors or inaccurate data, it was not discovered by the testers.  Generally, most people will want this.
 * Check the main [wiki:Home] page for updates on your class/spec.  If an issue is listed there as NOT fixed (or your class/spec hasn't been started yet), do not file a report, we know this already.  If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
 * Check the [tickets](https://sourceforge.net/p/whatsyourdamage/tickets) open and see if an issue was already reported. DO NOT REPORT THE SAME ISSUE as someone else.  Nobody wants to see 50 tickets saying the same thing.  Yours will be closed as a duplicate and ignored otherwise
 * Open a new [ticket](https://sourceforge.net/p/whatsyourdamage/tickets) using the following criteria:
-    - REQUIRED: Subject should be short but descriptive.  Example:  "LUA error upon login for (class - spec)"
-    - REQUIRED: Body should contain every item listed in the above testing criteria (You can even label it accordingly to make it easy to read).
-    - REQUIRED: Indicate which spec AND class you are testing. (For example:  If you say Holy, Restoration, or Frost without indicating the class, your ticket will be closed as invalid.)
-    - REQUIRED: Note ANY errors given when it is loaded in game.  Write them down, screenshot them, do whatever you can, but it is critical that the error be clear and complete.  Incomplete errors in a report WILL BE IGNORED (We cannot and will not troubleshoot something that you cannot report clearly)
-    - REQUIRED: Write down your pre-combat stats (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
-    - REQUIRED: Write down the numbers for each ability listed in the tooltips/actionbar (or screenshot will be fine) prior to combat
-    - REQUIRED: Write down your in-combat stats as you use an ability (screenshots are fine) (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
-    - REQUIRED: Write down the numbers listed in combat for said ability you think is wrong
-    - REQUIRED: Write down any relevant buffs you had (that may not be listed or explicitly stated in your above numbers) during and BEFORE combat
-    - REQUIRED: Write down any tier bonuses, trinkets, etc, you have.  You may also optionally (not instead of) include a link to your character in the armory if it will help us figure out what's going on.
-    - Add any relevant attachments in the ticket, but please understand that they should be in universally usable format (screenshots in jpg, png, gif, bmp format are fine), text captures in TEXT format are fine (DO NOT SEND WORD DOCUMENTS, Thanks).
-    - NOTE: Do not add opinions on tickets. State the facts and report what you are 'expecting' or 'unexpectedly' received.
-    - NOTE: Avoid long winded arguments (nobody wants to read it, I certainly don't either)
-    - NOTE: Do not ask unrelated questions to the issue at hand
-    - NOTE: Do not post in someone else's ticket to say "me too" (and anything like that) or chime in unless you can offer a fix or otherwise contribute to troubleshooting the problem.
-    - NOTE: Do not bump tickets to ask for an update. You'll get an update when project members can provide one.
-* NOTE: Do NOT pester any project member in game for support.  All support is done through this site ONLY.  (Trust me, nobody contributing to this will be able to answer an unending stream of questions.  You're not the only one using this mod, so consider that.)
+    - **REQUIRED**: Subject should be short but descriptive.  Example:  "LUA error upon login for (class - spec)"
+    - **REQUIRED**: Body should contain every item listed in the following criteria (You can even label it accordingly to make it easy to read):
+        1. **REQUIRED**:  Note your version number AND type - this is highly important.  Types are listed here:
+            -    Alpha: This code type is unstable and bound to have problems.  If you do not want to test potentially unstable, unfinished, or otherwise experimental code, do not use this.  Generally, only a small number of people should want to test this (usually a developer or a closed set of alpha testers).
+            -    Beta:  This code type is generally thought to be stable but may have a few lingering problems. Generally, more people will want to test this and will not be surprised if there are errors.
+            -    Release:    This code type is stable.  While it may have some unexpected errors or inaccurate data, it was not discovered by the testers.  Generally, most people will want this.
+        * **REQUIRED**: Indicate which spec AND class you are testing. (For example:  If you say Holy, Restoration, or Frost without indicating the class, your ticket will be closed as invalid.)
+        * **REQUIRED**: Note ANY errors given when it is loaded in game.  Write them down, screenshot them, do whatever you can, but it is critical that the error be clear and complete.  Incomplete errors in a report WILL BE IGNORED (We cannot and will not troubleshoot something that you cannot report clearly)
+        * **REQUIRED**: Write down your pre-combat stats (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
+        * **REQUIRED**: Write down the numbers for each ability listed in the tooltips/actionbar (or screenshot will be fine) prior to combat
+        * **REQUIRED**: Write down your in-combat stats as you use an ability (screenshots are fine) (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
+        * **REQUIRED**: Any procs active at the time of the issue (set bonuses, trinket procs, ability procs, etc.)
+        * **REQUIRED**: Write down the numbers listed in combat for said ability you think is wrong
+        * **REQUIRED**: Write down any buffs you had (that may not be listed or explicitly stated in your above numbers) during and BEFORE combat
+        * **REQUIRED**: Write down any tier bonuses, trinkets, etc, you have.  
+        * **OPTIONAL**: You may also include a link to your character in the armory if it will help us figure out what's going on - but make sure you are in the gear and spec on the armory for the one you are reporting.  
+        * **OPTIONAL**: World of Logs link to testing on a combat dummy are completely fine and probably cool enough to help troubleshoot.
+    - Add any relevant attachments in the ticket, but please understand that they should be in universally usable format (screenshots in jpg, png, gif, bmp format are fine), text captures in TEXT format are fine (**DO NOT SEND WORD DOCUMENTS**, Thanks).
+    - **NOTE**: Do not add opinions on tickets. State the facts and report what you are 'expecting' or 'unexpectedly' received.
+    - **NOTE**: Avoid long winded arguments (nobody wants to read it, I certainly don't either)
+    - **NOTE**: Do not ask unrelated questions to the issue at hand
+    - **NOTE**: Do not post in someone else's ticket to say "me too" (and anything like that) or chime in unless you can offer a fix or otherwise contribute to troubleshooting the problem.
+    - **NOTE**: Do not bump tickets to ask for an update. You'll get an update when project members can provide one.
+* **NOTE**: Do NOT pester any project member in game for support.  All support is done through this site ONLY.  (Trust me, nobody contributing to this will be able to answer an unending stream of questions.  You're not the only one using this mod, so consider that.)

WikiPage How To Properly Test modified by JustJ

JustJ — Fri, 18 Jan 2013 00:43:20 -0000

--- v6
+++ v7
@@ -7,17 +7,17 @@
     -    Release:    This code type is stable.  While it may have some unexpected errors or inaccurate data, it was not discovered by the testers.  Generally, most people will want this.
 * Check the main [wiki:Home] page for updates on your class/spec.  If an issue is listed there as NOT fixed (or your class/spec hasn't been started yet), do not file a report, we know this already.  If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
 * Check the [tickets](https://sourceforge.net/p/whatsyourdamage/tickets) open and see if an issue was already reported. DO NOT REPORT THE SAME ISSUE as someone else.  Nobody wants to see 50 tickets saying the same thing.  Yours will be closed as a duplicate and ignored otherwise
-* TICKET REQUIRED INFO: Note ANY errors given when it is loaded in game.  Write them down, screenshot them, do whatever you can, but it is critical that the error be clear and complete.  Incomplete errors in a report WILL BE IGNORED (We cannot and will not troubleshoot something that you cannot report clearly)
-* TICKET REQUIRED INFO: Write down your pre-combat stats (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
-* TICKET REQUIRED INFO: Write down the numbers for each ability listed in the tooltips/actionbar (or screenshot will be fine) prior to combat
-* TICKET REQUIRED INFO: Write down your in-combat stats as you use an ability (screenshots are fine) (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
-* TICKET REQUIRED INFO: Write down the numbers listed in combat for said ability you think is wrong
-* TICKET REQUIRED INFO: Write down any relevant buffs you had (that may not be listed or explicitly stated in your above numbers) during and BEFORE combat
-
 * Open a new [ticket](https://sourceforge.net/p/whatsyourdamage/tickets) using the following criteria:
     - REQUIRED: Subject should be short but descriptive.  Example:  "LUA error upon login for (class - spec)"
     - REQUIRED: Body should contain every item listed in the above testing criteria (You can even label it accordingly to make it easy to read).
     - REQUIRED: Indicate which spec AND class you are testing. (For example:  If you say Holy, Restoration, or Frost without indicating the class, your ticket will be closed as invalid.)
+    - REQUIRED: Note ANY errors given when it is loaded in game.  Write them down, screenshot them, do whatever you can, but it is critical that the error be clear and complete.  Incomplete errors in a report WILL BE IGNORED (We cannot and will not troubleshoot something that you cannot report clearly)
+    - REQUIRED: Write down your pre-combat stats (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
+    - REQUIRED: Write down the numbers for each ability listed in the tooltips/actionbar (or screenshot will be fine) prior to combat
+    - REQUIRED: Write down your in-combat stats as you use an ability (screenshots are fine) (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
+    - REQUIRED: Write down the numbers listed in combat for said ability you think is wrong
+    - REQUIRED: Write down any relevant buffs you had (that may not be listed or explicitly stated in your above numbers) during and BEFORE combat
+    - REQUIRED: Write down any tier bonuses, trinkets, etc, you have.  You may also optionally (not instead of) include a link to your character in the armory if it will help us figure out what's going on.
     - Add any relevant attachments in the ticket, but please understand that they should be in universally usable format (screenshots in jpg, png, gif, bmp format are fine), text captures in TEXT format are fine (DO NOT SEND WORD DOCUMENTS, Thanks).
     - NOTE: Do not add opinions on tickets. State the facts and report what you are 'expecting' or 'unexpectedly' received.
     - NOTE: Avoid long winded arguments (nobody wants to read it, I certainly don't either)

WikiPage How To Properly Test modified by JustJ

JustJ — Fri, 18 Jan 2013 00:37:47 -0000

--- v5
+++ v6
@@ -5,7 +5,7 @@
     -    Alpha: This code type is unstable and bound to have problems.  If you do not want to test potentially unstable, unfinished, or otherwise experimental code, do not use this.  Generally, only a small number of people should want to test this (usually a developer or a closed set of alpha testers).
     -    Beta:  This code type is generally thought to be stable but may have a few lingering problems. Generally, more people will want to test this and will not be surprised if there are errors.
     -    Release:    This code type is stable.  While it may have some unexpected errors or inaccurate data, it was not discovered by the testers.  Generally, most people will want this.
-* Check the main [wiki] page for updates on your class/spec.  If an issue is listed there as NOT fixed (or your class/spec hasn't been started yet), do not file a report, we know this already.  If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
+* Check the main [wiki:Home] page for updates on your class/spec.  If an issue is listed there as NOT fixed (or your class/spec hasn't been started yet), do not file a report, we know this already.  If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
 * Check the [tickets](https://sourceforge.net/p/whatsyourdamage/tickets) open and see if an issue was already reported. DO NOT REPORT THE SAME ISSUE as someone else.  Nobody wants to see 50 tickets saying the same thing.  Yours will be closed as a duplicate and ignored otherwise
 * TICKET REQUIRED INFO: Note ANY errors given when it is loaded in game.  Write them down, screenshot them, do whatever you can, but it is critical that the error be clear and complete.  Incomplete errors in a report WILL BE IGNORED (We cannot and will not troubleshoot something that you cannot report clearly)
 * TICKET REQUIRED INFO: Write down your pre-combat stats (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery

WikiPage How To Properly Test modified by JustJ

JustJ — Fri, 18 Jan 2013 00:36:48 -0000

--- v4
+++ v5
@@ -1,10 +1,13 @@
 All items are required in requesting help, feedback, or reporting a problem.  Failure to do so will result in your ticket being closed as invalid.  YOU HAVE BEEN WARNED. :-)

 1. Download the addon [here](https://sourceforge.net/p/whatsyourdamage/files).
-* TICKET REQUIRED INFO:  Note your version - this is highly important
+* TICKET REQUIRED INFO:  Note your version number AND type - this is highly important.  Types are listed here:
+    -    Alpha: This code type is unstable and bound to have problems.  If you do not want to test potentially unstable, unfinished, or otherwise experimental code, do not use this.  Generally, only a small number of people should want to test this (usually a developer or a closed set of alpha testers).
+    -    Beta:  This code type is generally thought to be stable but may have a few lingering problems. Generally, more people will want to test this and will not be surprised if there are errors.
+    -    Release:    This code type is stable.  While it may have some unexpected errors or inaccurate data, it was not discovered by the testers.  Generally, most people will want this.
 * Check the main [wiki] page for updates on your class/spec.  If an issue is listed there as NOT fixed (or your class/spec hasn't been started yet), do not file a report, we know this already.  If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
 * Check the [tickets](https://sourceforge.net/p/whatsyourdamage/tickets) open and see if an issue was already reported. DO NOT REPORT THE SAME ISSUE as someone else.  Nobody wants to see 50 tickets saying the same thing.  Yours will be closed as a duplicate and ignored otherwise
-* TICKET REQUIRED INFO: Note ANY errors given when it is loaded in game.  Write them down, screenshot them, do whatever you can, but it is critical that the error be clear and complete.  Incomplete errors in a report WILL BE IGNORED (I cannot and will not troubleshoot something that you cannot report clearly)
+* TICKET REQUIRED INFO: Note ANY errors given when it is loaded in game.  Write them down, screenshot them, do whatever you can, but it is critical that the error be clear and complete.  Incomplete errors in a report WILL BE IGNORED (We cannot and will not troubleshoot something that you cannot report clearly)
 * TICKET REQUIRED INFO: Write down your pre-combat stats (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
 * TICKET REQUIRED INFO: Write down the numbers for each ability listed in the tooltips/actionbar (or screenshot will be fine) prior to combat
 * TICKET REQUIRED INFO: Write down your in-combat stats as you use an ability (screenshots are fine) (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery

WikiPage How To Properly Test modified by JustJ

JustJ — Fri, 18 Jan 2013 00:25:15 -0000

--- v3
+++ v4
@@ -21,4 +21,4 @@
     - NOTE: Do not ask unrelated questions to the issue at hand
     - NOTE: Do not post in someone else's ticket to say "me too" (and anything like that) or chime in unless you can offer a fix or otherwise contribute to troubleshooting the problem.
     - NOTE: Do not bump tickets to ask for an update. You'll get an update when project members can provide one.
-* NOTE: Do NOT pester any project member in game for support.  What support I do, I do here.  (Trust me, nobody contributing to this will be able to answer an unending stream of questions.  You're not the only one using this mod, so consider that.)
+* NOTE: Do NOT pester any project member in game for support.  All support is done through this site ONLY.  (Trust me, nobody contributing to this will be able to answer an unending stream of questions.  You're not the only one using this mod, so consider that.)

WikiPage How To Properly Test modified by JustJ

JustJ — Fri, 18 Jan 2013 00:24:33 -0000

--- v2
+++ v3
@@ -2,7 +2,7 @@

 1. Download the addon [here](https://sourceforge.net/p/whatsyourdamage/files).
 * TICKET REQUIRED INFO:  Note your version - this is highly important
-* Check the main [wiki] page for updates on your class/spec.  If an issue is listed there as NOT fixed (or not started), do not file a report, we know this already.  If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
+* Check the main [wiki] page for updates on your class/spec.  If an issue is listed there as NOT fixed (or your class/spec hasn't been started yet), do not file a report, we know this already.  If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
 * Check the [tickets](https://sourceforge.net/p/whatsyourdamage/tickets) open and see if an issue was already reported. DO NOT REPORT THE SAME ISSUE as someone else.  Nobody wants to see 50 tickets saying the same thing.  Yours will be closed as a duplicate and ignored otherwise
 * TICKET REQUIRED INFO: Note ANY errors given when it is loaded in game.  Write them down, screenshot them, do whatever you can, but it is critical that the error be clear and complete.  Incomplete errors in a report WILL BE IGNORED (I cannot and will not troubleshoot something that you cannot report clearly)
 * TICKET REQUIRED INFO: Write down your pre-combat stats (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery

WikiPage How To Properly Test modified by JustJ

JustJ — Fri, 18 Jan 2013 00:22:36 -0000

--- v1
+++ v2
@@ -3,7 +3,7 @@
 1. Download the addon [here](https://sourceforge.net/p/whatsyourdamage/files).
 * TICKET REQUIRED INFO:  Note your version - this is highly important
 * Check the main [wiki] page for updates on your class/spec.  If an issue is listed there as NOT fixed (or not started), do not file a report, we know this already.  If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
-* Check the tickets open and see if an issue was already reported. DO NOT REPORT THE SAME ISSUE as someone else.  Nobody wants to see 50 tickets saying the same thing.  Yours will be closed as a duplicate and ignored otherwise
+* Check the [tickets](https://sourceforge.net/p/whatsyourdamage/tickets) open and see if an issue was already reported. DO NOT REPORT THE SAME ISSUE as someone else.  Nobody wants to see 50 tickets saying the same thing.  Yours will be closed as a duplicate and ignored otherwise
 * TICKET REQUIRED INFO: Note ANY errors given when it is loaded in game.  Write them down, screenshot them, do whatever you can, but it is critical that the error be clear and complete.  Incomplete errors in a report WILL BE IGNORED (I cannot and will not troubleshoot something that you cannot report clearly)
 * TICKET REQUIRED INFO: Write down your pre-combat stats (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
 * TICKET REQUIRED INFO: Write down the numbers for each ability listed in the tooltips/actionbar (or screenshot will be fine) prior to combat

WikiPage How To Properly Test modified by JustJ

JustJ — Fri, 18 Jan 2013 00:21:01 -0000

All items are required in requesting help, feedback, or reporting a problem. Failure to do so will result in your ticket being closed as invalid. YOU HAVE BEEN WARNED. :-)

Download the addon here.
TICKET REQUIRED INFO: Note your version - this is highly important
Check the main [wiki] page for updates on your class/spec. If an issue is listed there as NOT fixed (or not started), do not file a report, we know this already. If you do so anyway, your ticket will be closed as invalid and ignored otherwise.
Check the tickets open and see if an issue was already reported. DO NOT REPORT THE SAME ISSUE as someone else. Nobody wants to see 50 tickets saying the same thing. Yours will be closed as a duplicate and ignored otherwise
TICKET REQUIRED INFO: Note ANY errors given when it is loaded in game. Write them down, screenshot them, do whatever you can, but it is critical that the error be clear and complete. Incomplete errors in a report WILL BE IGNORED (I cannot and will not troubleshoot something that you cannot report clearly)
TICKET REQUIRED INFO: Write down your pre-combat stats (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
TICKET REQUIRED INFO: Write down the numbers for each ability listed in the tooltips/actionbar (or screenshot will be fine) prior to combat
TICKET REQUIRED INFO: Write down your in-combat stats as you use an ability (screenshots are fine) (Attack power for melee/hunters/tanks, Spell power for casters, combat rating AND percent (spell/melee/ranged depending on your class) for all stats: Hit, Expertise, Haste, Crit, Mastery
TICKET REQUIRED INFO: Write down the numbers listed in combat for said ability you think is wrong
TICKET REQUIRED INFO: Write down any relevant buffs you had (that may not be listed or explicitly stated in your above numbers) during and BEFORE combat
Open a new ticket using the following criteria:
- REQUIRED: Subject should be short but descriptive. Example: "LUA error upon login for (class - spec)"
- REQUIRED: Body should contain every item listed in the above testing criteria (You can even label it accordingly to make it easy to read).
- REQUIRED: Indicate which spec AND class you are testing. (For example: If you say Holy, Restoration, or Frost without indicating the class, your ticket will be closed as invalid.)
- Add any relevant attachments in the ticket, but please understand that they should be in universally usable format (screenshots in jpg, png, gif, bmp format are fine), text captures in TEXT format are fine (DO NOT SEND WORD DOCUMENTS, Thanks).
- NOTE: Do not add opinions on tickets. State the facts and report what you are 'expecting' or 'unexpectedly' received.
- NOTE: Avoid long winded arguments (nobody wants to read it, I certainly don't either)
- NOTE: Do not ask unrelated questions to the issue at hand
- NOTE: Do not post in someone else's ticket to say "me too" (and anything like that) or chime in unless you can offer a fix or otherwise contribute to troubleshooting the problem.
- NOTE: Do not bump tickets to ask for an update. You'll get an update when project members can provide one.
NOTE: Do NOT pester any project member in game for support. What support I do, I do here. (Trust me, nobody contributing to this will be able to answer an unending stream of questions. You're not the only one using this mod, so consider that.)