Wikilivros:Exemplos para testes: diferenças entre revisões

Origem: Wikilivros, livros abertos por um mundo aberto.
Conteúdo apagado Conteúdo adicionado
{{Em tradução}}: traduzindo w:en:Wikipedia:Template test cases, para explicar uso posterior com as predefinições
(Sem diferenças)

Revisão das 15h04min de 11 de outubro de 2009

Predefinição:How-to Predefinição:Shortcut

As predefinições são uma ferramenta muito poderosa do MediaWiki, mas é possível cometer erros muito facilmente, mesmo entre os usuários mais experientes. Por este motivo, as predefinições mais complexas devem ser acompanhadas de uma página para testes e alguns casos de teste para evitar bugs e outros problemas.


Esta página encontra-se em processo de tradução. A sua ajuda é bem vinda.

Em que tipo de predefinições isto deve ser usado?

It is recommended to apply the test case pattern to templates using ParserFunctions that can generate very different looking output, such as the ones that take many parameters, or the ones that have many branches of the #switch operator.

For navigational boxes, of which the outputs are almost identical on each transcluding page, the benefit may not outweight the time and effort.

Any template that is transcluded in thousands of pages should of course be tested before an edit is made.

Pŕe-requisitos

The template must be properly documented following Wikipedia:Template documentation.

Furthermore, the template should not have too many interleaving <includeonly> and <noinclude> blocks. Ideally there is only one <noinclude> block, placed at the bottom of the template, and containing the {{documentation}} template.

Como criar as subpáginas /testes e /casos de teste

1: Suppose your template is named Template:X. Create a subpage with the name Template:X/sandbox and another with Template:X/testcases. When these subpages are present, the green /doc box produced by {{documentation}} automatically provide links to them. Note that "/sandbox" and "/testcases" are spelled in all lower-case.

2: Copy only the code (everything that is not surrounded by <noinclude>) from your Template:X to Template:X/sandbox. And add the following at the end of the last line, in the same line:

<noinclude>

{{template sandbox notice}}
</noinclude>

In other words, the result should be:

[-- Template code --]<noinclude>

{{template sandbox notice}}
</noinclude>

Note! The template code must start directly before and physically touch the <noinclude> tag. Any blank space or newlines between the template code and the <noinclude> tag can cause the template to render unwanted spaces or newlines when used.

3: Copy a few transcluding examples from articles ({{X | .... }}) to your Template:X/testcases. In the test case subpage, duplicate each example, and for one copy of each example, replace X with X/sandbox. This is done so that you may compare the old and new outputs side by side in the future. Lastly, add the following line at the beginning of the test case page. It does not matter how many blank lines you put around it:

{{template test cases notice}}

4: Thus Template:X/testcases will look like this:

 {{template test cases notice}}

 {{X | foo}}
 {{X/sandbox | foo}}

 {{X | bar}}
 {{X/sandbox | bar}}

4b: To make differences easier to identify, you can use Template:Testcase to lay out your test cases. Then, test cases which are changed in the sandbox are highlighted so you can double check that the change was intentional.

Como usar as páginas posteriormente

  • Sync sandbox from the real template (i.e. step 2 above)
  • Have fun editing the sandbox
  • Verify the test cases
  • If everything looks good, copy the code from the sandbox to the real template

If you chose not to compare the new and old outputs side by side described at the last bullet point of the previous section, it is recommended to use a tabbed browser and open the test case subpage before changing the sandbox, and another after changing the sandbox. This can ensure that the differences are compared accurately.

Exemplos

Ver também