This page is a translated version of the page Extension:Pickle and the translation is 7% complete.
Manual de extensiones de MediaWiki
OOjs UI icon advanced-invert.svg
Estado de lanzamiento: experimental
Implementación Interfaz de usuario, Extracción de datos, API
Descripción Provides a basic on-site testing framework for Scribunto.
  • John Erling Blad (Jebladdiscusión)
Última versión 0.1.0
Política de compatibilidad Master mantiene la compatibilidad con versiones anteriores.
MediaWiki >= 1.33
Cambios de la base de datos No
Composer jeblad/pickle
Licencia GNU Licencia Pública general 2.0 o posterior
Ayuda Help:Pickle
  • $wgIndicator
  • $wgLogEntry
  • $wgExtractor
  • $wgCategory
  • $wgTAP
  • $wgInvokeSubpage
  • $wgTranslationPath
  • $wgDefaultNamespace
  • $wgRenderTypes
  • $wgObserverID
  • $wgSetup
  • $wgExtractStatus
  • $wgExtractorPath
  • $wgNeglectSubpages
  • $wgTranslationFollows
  • $wgRenderPath
  • $wgRenderStyles
Traduce el Pickle extensión

The Pickle (or Behavior-driven development, BDD, previously Spec) extension is an extension for "spec" style testing for Scribunto . Spec type testing is the same type of unit testing that is done in Rspec, Busted and other similar testing frameworks. It will provide a very thin integration to PHP and a few Lua modules and their localizations. The actual code is still valid Lua, and all editing tools will work, except for missing definitions for intellisense in the various editors.

The extension is called Pickle because you pick on your code. It is also a play with words; gherkins are used for pickles. Gherkin is also a language for "step" style testing, a kind of acceptance testing, so you might say these kinds of code snippets are pickles. At some time in the future the extension might be extended with step style testing, and then the name would fit even better.

An overview of the pickle extension from a user perspective can be found at Help:Pickle .


The code at Phabricator might lag behind the code at GitHub: jeblad/Pickle, the later is used during development and might be unstable. Spec depends on the Scribunto extension. For recreating the Vagrant-based development environment, see Pickle: Topics/Vagrant.

  • Descarga y extrae los archivos en un directorio denominado «Pickle» dentro de la carpeta extensions/.
  • Añade el siguiente código en la parte final de tu LocalSettings.php :
    wfLoadExtension( 'Pickle' );
  •   Hecho – Navega a Special:Version en el wiki para verificar que la extensión se haya instalado correctamente.


The extension can be configured for implicit style or explicit style of tests. The implicit style piggybacks the installation on the describe() call, but this depends on a functional getfenv() call. The Scribunto extension limits the getfenv() call, and according to Extension:Scribunto/Lua reference manual#Differences from standard Lua it is not quite predictable, thus only the explicit style will work.

The reason for the dependency on getfenv() is that the functions are constructed before the describe() function is called, and thus the calling run-time environment are bound without the global functions. To insert the global functions in the correct run-time environment the describe() call use getfenv(). Without the getfenv() call the correct run-time environment must be present while creating the functions. Thus a call describe() must install the global functions.

Switching between the styles are done by the config { "Setup": "implicit" } or { "Setup": "explicit" }.

If you have a module like "Module:HelloWorld", the ubiquitous and quite pesky example, it will be coded as something like

local p = {}

function p.helloWorld()
	return "Hi there!"

return p

Then on a subpage /pickle you would test this like like the following

Implicit form
return describe 'Hello world' (function()
	subject .helloWorld()
	it 'says hello' (function()
		expect :toBe("Hi there!");
Explicit form

describe 'Hello world' (function()
	subject .helloWorld()
	it 'says hello' (function()
		expect :toBe("Hi there!");

return mw.pickle:reports()

The implicit form has the lines in the beginning and end removed, and the return statement moved down to the new end of code.

There might be additional changes, like where the tap() call is available, and how many describe() calls that can be made.