Template talk:Testing/start

Should a "Release" or "Region" section be added to the testing table to capture US vs EU vs JP releases? Kolano 05:20, 11 March 2011 (CET)

I think that is not necessary, only a few games (around 5 games) have region-specific issues. Jhonn 20:55, 11 March 2011 (CET)

Tester = User Link
My edits to put my user link in my test reports keep getting reverted. What is the thinking behind this? Is it causing a back end issue to have a user link? I am trying to follow existing procedures -- based on Template:Testing/doc, you're SUPPOSED to use a user link. --Keller999 08:30, 18 August 2011 (CEST)
 * Okay, I see why now -- the template should be autogenerating a user link if I'm a user. When you revert my edits, just give me a 5 word explanation -- "This should happen automatically" would have resolved a lot of frustration early!  'preciate it. --Keller999 09:36, 18 August 2011 (CEST)

Android testing results
I recently saw some users posting test results of Dolphin for Android in the forums. Should we start including them in the wiki? Jhonn (talk)

We can, I may need to make some template edits to handle categories, documentation updates, and etc for such. Kolano (talk) 08:28, 1 May 2014 (CEST)

The main problem I see is that... will users even know what's in their phones? Sure they will possibly know what their phone is, so I guess that gives us something to work from, but are you ok with getting CPU and GPU information from a phone name? And how to phone names fit in the template? - MaJoR (talk) 16:30, 5 May 2014 (CEST)

Well, if the user want to upload an Android test then we should require they at least know what CPU and GPU their phone have. Another possible (but a little ugly) solution would be matching CPU and GPU from a table (maybe in a sub template) with phone names to do the thing, so, in the test entry the user would just put something like this: and in the page it would be replaced by the common template (Revision=4.0-xxx, OS=Android 4.3, CPU=Krait 400 Quad Core @ 2.26GHz, GPU=Adreno 330). The main issue with this approach would be the big nightmares we would get, like maintaining the list updated with all of Android phones available, not to mention having a lot of entries for the same phone in the sub template table (Samsung Galaxies for example, flagship models get at least a Qualcomm variant and an Exynos variant in most cases) Jhonn (talk)