Template:Testing/doc - Revision history

Sonicadvance1: /* Example */

2025-05-03T00:02:43Z

Example

MayImilae: /* Example */

2020-10-28T07:04:18Z

Example

MayImilae: /* Example */

2020-10-26T06:58:11Z

Example

MayImilae: Copied from Dolphin-emu

2020-10-23T05:52:16Z

Copied from Dolphin-emu

New page

== About ==
This three-part '''testing''' template should be used to display details of testing against a particular game. Use the {{tl|testing/start}} template to add rows but remember to use the rules listed in the "parameters" section below. Please list entries in chronological order; oldest to newest, top to bottom.

=== Neighboring Templates ===
* [[Template:Testing/start]]
* [[Template:Testing/entry]]
* [[Template:Testing/end]]

== Example ==
<pre>
{{testing/start}}
{{testing/entry|revision=4.0-7654|OS=Windows 7|CPU=Intel Core i5-4690K @ 3.5GHz|GPU=NVIDIA GeForce GTX 960|result=Intro slow, but in game full speed.|tester=User name}}
{{testing/end}}
</pre>

Produces
<div style="background:#fff;border:1px solid #ddd;padding:.5em">
{{testing/start}}
{{testing/entry|revision=4.0-7654|OS=Windows 7|CPU=Intel Core i5-4690K @ 3.5GHz|GPU=NVIDIA GeForce GTX 960|result=Intro slow, but in game full speed.|tester=User name}}
{{testing/end}}</div>

== Parameters ==
=== Start ===
<pre>{{testing/start}}</pre>
No parameters needed.

=== Entry ===
<pre>{{testing/entry|revision=|OS=|CPU=|GPU=|result=|tester=}}</pre>
*In <code>|revision=</code> you should specify revision number like you would do with {{tl|Revision}} (The same rules apply here, so any special handling described in {{tl|Revision}} will work too).
*In <code>|OS=</code> you should provide basic details of your operating system, like OS Brand + Version (e.g. Windows 7, Mac OS X 10.10, Ubuntu 15.04, Android 5.1, etc). For Linux test entries you should specify the official distro naming followed by version. Also, avoid listing OS edition (e.g. Windows 7 Home Premium) and use a version number instead of a release name whenever possible (e.g. Debian 7 instead of Debian Wheezy, Android 5.1 instead of Android Lollipop, Mac OS X 10.10 instead of Mac OS X Yosemite, etc).
*In <code>|CPU=</code> you should provide only basic information, like CPU Brand + Series + Model + @ + Frequency in GHz (e.g. Intel Core i5-6700K @ 4GHz, AMD FX-6300 @ 3.5GHz). On CPUs with variable clock speed features (like Intel Turbo Boost or AMD Turbo Core) you should provide the base clock or, if overclocked, the frequency you were using when testing (e.g. Intel Pentium G3258 @ 4.2GHz). Other details such as number of cores, cache size, architecture and similar are not needed and should not be listed.
*In <code>|GPU=</code> the same guidelines from CPU applies here as well, provide basic information like GPU Brand + Series + Model (e.g. AMD Radeon R9 290X, AMD Radeon HD 7990, NVIDIA GeForce GTX 970, NVIDIA GeForce GTX Titan X, Intel HD Graphics 4600, etc). Other details such as GPU Maker, whether it's a factory overclocked model or not, VRAM size and similar are not needed and should not be listed either.
*In <code>|results=</code> write a brief description of how Dolphin performed (e.g. "Playable: 40-60 FPS, intro slow" or "Slow: 25-35 FPS in game due slow CPU").
*In <code>|tester=</code> you should list your nickname or alias, it'll automatically link to a user page if a wiki account with the same name/alias exists.

=== End ===
<pre>{{testing/end}}</pre>
No parameters needed.

@@ Line 17: / Line 17: @@
 <div style="background:#fff;border:1px solid #ddd;padding:.5em">
 {{testing/start}}
-{{testing/entry|revision=4.0-7654|archtitle=x86-64|archhost=x86-64|result=Intro slow, but in game full speed.|tester=User name}}
+{{testing/entry|revision=4.0-7654|archtitle=x86-64|result=Intro slow, but in game full speed.|tester=User name}}
 {{testing/end}}</div>