IMO this is where that consolidated error grabbing & uploading comes in handy.
Much like bug grabber and bugsack combo, but one that uploads those errors to a central source. Could even add an ability to file a ticket in game with the default ticket templates & the cc uploads them on logout / reload. Now that would be useful.
Something that the curse client could be cajoled into handling. Even so, CC4 auto uploads error report to it's project on curseforge iirc, granted it's one project with a knonw error source.
Granted the problem is assigning blame to where the error came from. There was a thread on this some time ago, tho it didn't go anywhere.
That's not really that useful because it only benefits people who both use the Curse reporting system and the Curse Client in general. Better off putting work into identifying the addon that caused it, then letting the addon specifically tell the user "Hey go to X to report the error for this mod," all the user pretty much does is look at the first folder of the error and blame that mod anyway :<
Remember that we are talking about encouraging testers to provide feedback that is not necessarily limited to in-game errors. Part of this process involves a means of providing directions or instructions to testers for new features or desirable testing scenarios.
The changelog is a good place to start for this, but I would certainly understand if authors wished to provide instructions more blatantly within the game itself.
The specific addon I'm referring to is called AuctionMaster. Give it a shot and see if it's too obtrusive. Although the change log is a REALLY good place to, you know, put changes.
IMO this is where that consolidated error grabbing & uploading comes in handy.
Much like bug grabber and bugsack combo, but one that uploads those errors to a central source. Could even add an ability to file a ticket in game with the default ticket templates & the cc uploads them on logout / reload. Now that would be useful.
Something that the curse client could be cajoled into handling. Even so, CC4 auto uploads error report to it's project on curseforge iirc, granted it's one project with a knonw error source.
Granted the problem is assigning blame to where the error came from. There was a thread on this some time ago, tho it didn't go anywhere.
I'm not a fan of popups either. Broker might work, how about .testalert for a field? That could be routed to pretty much anything or nothing.
I ment using a new value for the type field. And then somebody just needs to create an addon like tekkub's MakeRocketGoNow where they all get listed under a single LDB datasource plugin. Maybe have a field for the date the stuff in the broker feed was last changed for each addon (not the last commit date for the addon) and sort them by that. Could even agree on some more standard fields and allow for each one to be clicked on to bring up a standard window with more detailed info or let the addon say it has its own window it wants opened when clicked.
I sincerely doubt that any sort of solution that relies on testers to have an addon installed to know what they should test will have much success.
It would probably have to fall back on using a popup or chat message, but it would be nice to give the testers the option of collecting the messages in a better place if the practice of login-time tester instructions becomes widespread.
Popping a message in the chat window still seems like the best way to me.
Except that some people run addons that block login-time chat window spam, and most people who don't still ignore it because there's so much (which reminds me that I need to turn some stuff off in a few addons to reduce that on my UI).
Yesterday I set up a clone of stack overflow with the intention of using it as part of the error reporting tool I had talked about last year in the post i linked above.
I sort of see some overlap between the goals of that project, and what is being discussed in this thread.
Perhaps we can join forces on this. For the error reporting system i described, and the tester information system you are describing, you need at the very least a way to get information to (and from) your testers in-game. The information on what to test, could very easily contain what info to collect if a bug is found, and it would follow then that being able to store that, and make sure its uploaded to the right place is all part of the same goal.
I sort of envision the web site being used as a 'hub' for testers. Sort of like a bug tracker, but not exactly. The one case I am thinking of is "I get some error X, but what addon is causing it".
It would probably have to fall back on using a popup or chat message ...
I'd still argue against this. If you want testing of a specific feature, say so in the changelog. Users who are interested and able to test and provide feedback are probably the same users who read the changelogs, so we will see it. Putting in some "feature" to spam us with chat messages or popups every time we download a new alpha or beta is simply obnoxious, and would probably have the opposite of the desired effect. Personally, I would start looking for alternative addons, or just not updating. One-time popups like the one used in AtlasLoot are annoying enough.
Maybe instead of a popup, a LDB icon that basically collects all of them into one spot - it's non-intrusive and easily ignored if you don't feel like dealing with it on raid day :P.
While I see Phanx's point about people reading changelogs, I think the idea is to coerce more people into helping - so the changelog thing preaches to the choir, it's the people outside that need the pamphlets.
Well, I can't recall ever seeing a specific request for testing with a specific change in a changelog, and only a handful of vague comments implying that testing might be welcome. So... while it may be preaching to the choir, the choir hasn't heard any sermons in a while. :p
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumMuch like bug grabber and bugsack combo, but one that uploads those errors to a central source. Could even add an ability to file a ticket in game with the default ticket templates & the cc uploads them on logout / reload. Now that would be useful.
Something that the curse client could be cajoled into handling. Even so, CC4 auto uploads error report to it's project on curseforge iirc, granted it's one project with a knonw error source.
Granted the problem is assigning blame to where the error came from. There was a thread on this some time ago, tho it didn't go anywhere.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe changelog is a good place to start for this, but I would certainly understand if authors wished to provide instructions more blatantly within the game itself.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttp://forums.wowace.com/showthread.php?t=14479&highlight=error+reporting
Yeah - totally went nowhere.
I ment using a new value for the type field. And then somebody just needs to create an addon like tekkub's MakeRocketGoNow where they all get listed under a single LDB datasource plugin. Maybe have a field for the date the stuff in the broker feed was last changed for each addon (not the last commit date for the addon) and sort them by that. Could even agree on some more standard fields and allow for each one to be clicked on to bring up a standard window with more detailed info or let the addon say it has its own window it wants opened when clicked.
Popping a message in the chat window still seems like the best way to me.
It would probably have to fall back on using a popup or chat message, but it would be nice to give the testers the option of collecting the messages in a better place if the practice of login-time tester instructions becomes widespread.
Except that some people run addons that block login-time chat window spam, and most people who don't still ignore it because there's so much (which reminds me that I need to turn some stuff off in a few addons to reduce that on my UI).
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI sort of see some overlap between the goals of that project, and what is being discussed in this thread.
Perhaps we can join forces on this. For the error reporting system i described, and the tester information system you are describing, you need at the very least a way to get information to (and from) your testers in-game. The information on what to test, could very easily contain what info to collect if a bug is found, and it would follow then that being able to store that, and make sure its uploaded to the right place is all part of the same goal.
You really would need to read this thread (http://forums.wowace.com/showthread.php?t=14479&highlight=error+reporting) about error reporting for this next part to make sense. This post is the most relevant (http://forums.wowace.com/showpost.php?p=244926&postcount=40)
I sort of envision the web site being used as a 'hub' for testers. Sort of like a bug tracker, but not exactly. The one case I am thinking of is "I get some error X, but what addon is causing it".
Anyhow here's the site link:[snip]
I'd still argue against this. If you want testing of a specific feature, say so in the changelog. Users who are interested and able to test and provide feedback are probably the same users who read the changelogs, so we will see it. Putting in some "feature" to spam us with chat messages or popups every time we download a new alpha or beta is simply obnoxious, and would probably have the opposite of the desired effect. Personally, I would start looking for alternative addons, or just not updating. One-time popups like the one used in AtlasLoot are annoying enough.
While I see Phanx's point about people reading changelogs, I think the idea is to coerce more people into helping - so the changelog thing preaches to the choir, it's the people outside that need the pamphlets.