This module runs unit tests to compare template output with expected text. In addition, the module can output the results of expanding templates.
While intended for testing, the tester should be useful with other templates that require many tests using a simple format for the test input.
It is not necessary to save the testcases page before viewing test results. For example, could be edited to change the tests. While still editing that page, paste (without quotes) into the page title box under "Preview page with this template", then click "Show preview".
The testcases talk page (for example,) contains:
{{#invoke:convert/sandbox/testcases|run_tests}}
The testcases module page (for example,) may contain:
]
local p = require('Module:Convert/tester')p.tests = testsreturn p
If wanted, the tests can be run using a template different from the one specified in the tests. For example, the following would run the tests from, but would change the name of each template found on that page to "convert/sandbox2".
{{#invoke:convert/sandbox/testcases|run_tests|template=convert/sandbox2}}
Tests are extracted from a multiline string. Any line that does not start with a template is ignored. Each processed line starts with a template, and is followed by whitespace, then the wikitext which should result from expanding the template.
The expected output must be entered in a single line. If the template outputs multiple lines, those lines must be joined with "\n" (two characters—backslash n).
The templates do not have to be the same, for example, the following tests would work:
In the results, the status column shows "Pass" if the output from the template exactly matches the expected text. If there is no expected text, the template output is shown in the Actual column with a blank status. If the given expected text differs from the template output, the template output is shown in the Actual column with status "Fail", and the number of fails is shown at the top of the page. Searching the page for "Fail" will find each problem. Any "Fail" result is followed by a row showing the nowiki actual and expected wikitext.
If using a testcases module (as in the above example), the test text is assigned to p.tests before executing run_tests.
Alternatively, the test text can be read from any page, or from any section on any page. For example, the following wikitext could be entered in a sandbox:
== Mixed tests ==
<pre>
{{convert|12|m}} 12 metres (39 ft)
{{convert/sandbox|0.16|/l|2|disp=table}} align="right"|0.16\n|align="right"|0.61
{{age in days|2007|5|24|2008|4|23}} 335
--- The following line is incorrect to demonstrate a "fail".
{{convert|12|m|lk=on}} 12 [[meter|metres]] (39 [[Foot|ft]])
The following line demonstrates the result when no expected text is provided.
{{convert/sandbox|1|-|5|in|mm|lk=on}}
</pre>
Given the above, the tests can be run as shown in the following section.
Instead of specifying the tests with a multiline string, it is possible to assign a table to p.tests as shown in the following testcases module.
local p = require('Module:Convert/tester')p.tests = testsreturn p
This example provides the same results as the multiline string at "Mixed tests" above.
Entering either of the following lines of wikitext in a sandbox or talk page would run the tests found at the specified location. The first line would show all tests on page "Template talk:Example", while the second would show only those tests on that page that are in the "Mixed tests" section.
{{#invoke:convert/tester|run_tests|page=Template talk:Example}}
{{#invoke:convert/tester|run_tests|page=Template talk:Example|section=Mixed tests}}
As a demonstration, the following line is used to produce the table shown below, including the comment that starts with three dashes.
{{#invoke:convert/tester|run_tests|page=Module:Convert/tester/doc|section=Specifying tests|show=all}}
Function make_tests can be used to create tests in the format expected by run_tests. For example, previewing either of the following in a sandbox would show the results from expanding each template found on the specified page.
{{#invoke:convert/tester|make_tests|page=Template talk:Example}}
{{#invoke:convert/tester|make_tests|page=Template talk:Example|show=all}}
When using make_tests, any expected results in the input are ignored. Instead, the module shows each template and its actual output as plain text which can be copied to make a testcases page. The templates to be processed can be specified by setting p.tests or by specifying a page with an optional section.
If |show=all is included, any non-template lines are included in the result. The output could then be copied and used to replace the page with the tests in order to update the expected text for each template, but without changing non-template lines.
As a demonstration, the following line is used to produce the text shown below.
{{#invoke:convert/tester|make_tests|page=Module:Convert/tester/doc|section=Specifying tests}}
The |show=all option can be used with make_tests and with run_tests.
An example using make_tests is shown in the previous section.
Using |show=all with run_tests allows comment lines to be displayed in the output table—not all lines are shown, only those that start with three dashes. For example, the testcases may include the following.
Added 12 January 2014.
--- The following tests check the widget option.
{{example|1|2|widget=on}} ...(expected output)...
The table produced by run_tests would show "The following tests check the widget option." as a comment line, but only if |show=all is used. Comments have a distinctive background color, but also show "Cmnt" in the status column so they can be found by searching.
When viewing a module, the documentation page is displayed; if the module has a sandbox, the documentation includes "Editors can experiment in this module's sandbox" with a link to diff the module and its sandbox.
The tester module provides a compare function which can check a series of modules, and compare each with its sandbox. A table is displayed showing whether the content is different, with a diff link.
For example, the following wikitext could be used.
{{#invoke:convert/tester|compare|Example|Example/data}}
The names "Example" and "Example/data" do not include a colon (:), so "Module:" is assumed. The command compares Module:Example with Module:Example/sandbox, and Module:Example/data with Module:Example/data/sandbox.
It is also possible for a module to define pairs of page titles in p.pairs (a table), and to use the tester module to generate a table for each pair of titles.
As a convenience, certain keywords are defined. If a keyword is recognized, the list of pairs comes from the module rather than the parameters. For example, the following uses the "convert" keyword to get the list of pairs of pages related to Module:Convert.
{{#invoke:convert/tester|compare|convert}}
The following text is a sample showing output that may result from the above.
By default, each output line is prefixed with '*' to give a bulleted list. An alternative prefix can be specified with the prefix parameter. For example, the following gives an indented bulleted list.
{{#invoke:convert/tester|compare|convert|prefix=:*}}