Lettuce v0.1.34 (barium release) documentation
Home
|
Table of contents
|
Index
|
|
next
»
Lettuce documentation contents
¶
nutshell
getting involved !
hands on!
introduction
what the feature ?!
walkthrough
integrate!
furthermore
recipes
Overview
On BDD
Introducing Lettuce
Lettuce pragma
Hands on!
Installing Lettuce
Stable release
Using control version’s HEAD
Build and install the egg from sources
Use the latest code to contribute with lettuce’s codebase
What the f** eature ?
Features
Scenarios
Simple
Outlined
Steps and its definitions
Simple steps
Tabular steps
introduction
get lettuce
define a problem
project structure
lettuce it!
first round
[a] describe behaviour
[b] define steps in python
[c] run and watch it fail
[d] write code to make it pass
[e] run again and watch it pass
second round
[a] describe behaviour
[b] define steps in python
[c] run and watch it fail
[d] write code to make it pass
[e] run again and watch it pass
third round
[a] describe behaviour
[b] define steps in python
[c] run and watch it fail
[d] write code to make it pass
[e] run again and watch it pass
forth round
handling data with tables
multi-line strings
scenario outlines
calling steps from step definitions
running blocks of steps
the command line
running a specific feature file
running only some scenarios of a specific feature file
running only some scenarios all feature files
verbosity levels
level 1 - dots for each feature
level 2 - scenario names
level 3 - full feature print, but colorless
level 4 - full feature print, but colorful
getting help from shell
features, scenarios and steps reference
Feature
Feature.name
Feature.scenarios
Feature.described_at
Feature.max_length
Feature.get_head
TotalResult
TotalResult.features_ran
TotalResult.features_passed
TotalResult.scenarios_ran
TotalResult.scenarios_passed
TotalResult.steps
TotalResult.proposed_definitions
Scenario
Scenario.steps
Step
Step.sentence
step definition
the “terrain”
terrain.py
in practice
world
in practice
world.absorb
world.spew
hooks
@before.all
@after.all
@before.each_feature
@after.each_feature
@before.each_scenario
@after.each_scenario
@before.each_step
@after.each_step
django-specific hooks
@before.harvest
@after.harvest
@before.each_app
@after.each_app
@before.runserver and @after.runserver
@before.handle_request and @after.handle_request
language support
writing features in a specific language
english example
brazilian portuguese example
adding support to other languages
fetch the code
add your translation
Lettuce recipe: Using nose for pretty assertions
Web development fun with Lettuce and Django
Getting started
1. install the lettuce django app
2. create the feature directories
3. write your first feature
4. run the tests
5. specifying feature files
6. grab actual example code
Technical details
red-tape-less builtin server
figure out django urls
what does
django_url
do ?!?
terrain also available in django projects
Running without HTTP server
running the HTTP server in other port than 8000
running the HTTP server with settings.DEBUG=True
running only the specified scenarios
to run or not to run? That is the question!
running tests from just certain apps
running tests from all apps, except by some
Development guidelines
Synopsis
Table of contents
Install a development environment for lettuce
Testing
Contributing to the documentation
Keep in mind
References
Indices, glossary and tables
¶
Index
Module Index
Table Of Contents
Lettuce documentation contents
Indices, glossary and tables
Browse
Next:
nutshell
You are here:
Lettuce v0.1.34 (barium release) documentation
Lettuce documentation contents
This Page
Show Source
Quick search
Enter search terms or a module, class or function name.
Last update:
Jan 22, 2012
|
next
»