Dashboard > GreenPepperOpen > Documentation > Reading and understanding the executable specification
  GreenPepperOpen Log In View a printable version of the current page.  
  Reading and understanding the executable specification
Added by AndrĂ© Brissette, last edited by fhatem on Jul 17, 2007  (view change)
Labels: 
(None)

Reading and understanding a GreenPepper Executable Specification

A GreenPepper Executable Specification is a document mainly composed of free text and GreenPepper examples.
As a GreenPepper example we mean an executable structure that will be interpreted over the System under test.

I. The GreenPepper Example forms.

  1. Table (Most common form).
    • The first cell is reserved to the Interpreter which will dictacte the exact table structure.
      My Interpreter ...
      ... ...
    • The Second cell is reserved to the Fixture.
      My Interpreter My Fixture
      ... ...
    • The Third cell is an optional comment that is ignored by GreenPepper .
      My Interpreter My Fixture good old comment
      ... ...
    • Every other cells following the fixture name is a parameter separated by a comment cell.
      My Interpreter My Fixture comment parameter 1 to My Fixture comment second parameter
      ... ...

Ex: | rule for | product listing | sorting using | ascending | order |

rule for -> interpreter
product listing -> fixture name
sorting using, order -> comments
ascending -> parameter to product listing fixture

    • Table headers <th><\th> are supported and interpreted like normal table elements.
    • The table doesn't have to be rectangular.
      This is a valid GreenPepper example
      a b sum()
      1 2 3


  1. Bullet list
    • Cell simulation with <style> such as: bold italic ...

Interpreters (GreenPepperOpen)
DEMONSTRATION LICENSE - This Confluence site is for demonstration purposes only. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.4.3 Build:#705 Mar 21, 2007) - Bug/feature request - Contact Administrators