Skip to content

@after_all (and possibly other) decorators not behaving properly. #44

@wholewheattoast

Description

@wholewheattoast

@after_all seems to be firing after every feature run, not after all the features.

A run with lettuce
screen shot 2014-08-06 at 2 46 27 pm

A run with lettuce_webdriver
screen shot 2014-08-06 at 2 45 41 pm

Test is the example from lettuce.it

With a second copy of the feature to have more then one feature running. I can gist the tests if needed.

Each test done in it's own virturalenv against the same exact /feature directory.

The terrain file looks like

from lettuce import *

@after.all
def say_goodbye(total):
    report_message = "%d of %d scenarios passed." % (
        total.scenarios_passed,
        total.scenarios_ran
    )

    print report_message
    print "After All -- Goodbye!"

@after.each_feature
def teardown_some_feature(feature):
    print "The feature %r just has just ran" % feature.name

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions