How to skip the rest of tests in the class if one has failed?

Posted on

Question :

How to skip the rest of tests in the class if one has failed?

I’m creating the test cases for web-tests using Jenkins, Python, Selenium2(webdriver) and Py.test frameworks.

So far I’m organizing my tests in the following structure:

each Class is the Test Case and each test_ method is a Test Step.

This setup works GREAT when everything is working fine, however when one step crashes the rest of the “Test Steps” go crazy. I’m able to contain the failure inside the Class (Test Case) with the help of teardown_class(), however I’m looking into how to improve this.

What I need is somehow skip(or xfail) the rest of the test_ methods within one class if one of them has failed, so that the rest of the test cases are not run and marked as FAILED (since that would be false positive)


UPDATE: I’m not looking or the answer “it’s bad practice” since calling it that way is very arguable. (each Test Class is independent – and that should be enough).

UPDATE 2: Putting “if” condition in each test method is not an option – is a LOT of repeated work. What I’m looking for is (maybe) somebody knows how to use the hooks to the class methods.

Answer #1:

I like the general “test-step” idea. I’d term it as “incremental” testing and it makes most sense in functional testing scenarios IMHO.

Here is a an implementation that doesn’t depend on internal details of pytest (except for the official hook extensions). Copy this into your

import pytest

def pytest_runtest_makereport(item, call):
    if "incremental" in item.keywords:
        if call.excinfo is not None:
            parent = item.parent
            parent._previousfailed = item

def pytest_runtest_setup(item):
    previousfailed = getattr(item.parent, "_previousfailed", None)
    if previousfailed is not None:
        pytest.xfail("previous test failed (%s)" %

If you now have a “” like this:

import pytest

class TestUserHandling:
    def test_login(self):
    def test_modification(self):
        assert 0
    def test_deletion(self):

then running it looks like this (using -rx to report on xfail reasons):

(1)hpk@t2:~/p/pytest/doc/en/example/teststep$ py.test -rx
============================= test session starts ==============================
platform linux2 -- Python 2.7.3 -- pytest-2.3.0.dev17
plugins: xdist, bugzilla, cache, oejskit, cli, pep8, cov, timeout
collected 3 items .Fx

=================================== FAILURES ===================================
______________________ TestUserHandling.test_modification ______________________

self = <test_step.TestUserHandling instance at 0x1e0d9e0>

    def test_modification(self):
>       assert 0
E       assert 0 AssertionError
=========================== short test summary info ============================
  reason: previous test failed (test_modification)
================ 1 failed, 1 passed, 1 xfailed in 0.02 seconds =================

I am using “xfail” here because skips are rather for wrong environments or missing dependencies, wrong interpreter versions.

Edit: Note that neither your example nor my example would directly work with distributed testing. For this, the pytest-xdist plugin needs to grow a way to define groups/classes to be sent whole-sale to one testing slave instead of the current mode which usually sends test functions of a class to different slaves.

Answered By: hpk42

Answer #2:

Answered By: gbonetti

Answer #3:

It’s generally bad practice to do what are you doing. Each test should be as independent as possible from the others, while you completely depend on the results of the other tests.

Anyway, reading the docs it seems like a feature like the one you want is not implemented.(Probably because it wasn’t considered useful).

A work-around could be to “fail” your tests calling a custom method which sets some condition on the class, and mark each test with the “skipIf” decorator:

class MyTestCase(unittest.TestCase):
    skip_all = False

   def test_A(self):
        if failed:
            MyTestCase.skip_all = True
  def test_B(self):
      if failed:
          MyTestCase.skip_all = True

Or you can do this control before running each test and eventually call pytest.skip().

Marking as xfail can be done in the same way, but using the corresponding function calls.

Probably, instead of rewriting the boiler-plate code for each test, you could write a decorator(this would probably require that your methods return a “flag” stating if they failed or not).

Anyway, I’d like to point out that,as you state, if one of these tests fails then other failing tests in the same test case should be considered false positive…
but you can do this “by hand”. Just check the output and spot the false positives.
Even though this might be boring./error prone.

Answered By: Bakuriu

Answer #4:

You might want to have a look at pytest-dependency. It is a plugin that allows you to skip some tests if some other test had failed.
In your very case, it seems that the incremental tests that gbonetti discussed is more relevant.

Answered By: azmeuk

Answer #5:

The pytest -x option will stop test after first failure:
pytest -vs -x

Answered By: Parth Naik

Answer #6:

UPDATE: Please take a look at @hpk42 answer. His answer is less intrusive.

This is what I was actually looking for:

from _pytest.runner import runtestprotocol
import pytest
from _pytest.mark import MarkInfo

def check_call_report(item, nextitem):
    if test method fails then mark the rest of the test methods as 'skip'
    also if any of the methods is marked as 'pytest.mark.blocker' then
    interrupt further testing
    reports = runtestprotocol(item, nextitem=nextitem)
    for report in reports:
        if report.when == "call":
            if report.outcome == "failed":
                for test_method in item.parent._collected[item.parent._collected.index(item):]:
                    if test_method.keywords.has_key('blocker') and isinstance(test_method.keywords.get('blocker'), MarkInfo):
                        item.session.shouldstop = "blocker issue has failed or was marked for skipping"

def pytest_runtest_protocol(item, nextitem):
# add to the hook
        nodeid=item.nodeid, location=item.location,
    check_call_report(item, nextitem)
    return True

Now adding this to or as a plugin solves my problem.
Also it’s improved to STOP testing if the blocker test has failed. (meaning that the entire further tests are useless)

Answered By: Alex Okrushko

Answer #7:

Or quite simply instead of calling py.test from cmd (or tox or wherever), just call:

py.test --maxfail=1

see here for more switches:

Answered By: theQuestionMan

Answer #8:

To complement hpk42’s answer, you can also use pytest-steps to perform incremental testing, this can help you in particular if you wish to share some kind of incremental state/intermediate results between the steps.

With this package you do not need to put all the steps in a class (you can, but it is not required), simply decorate your “test suite” function with @test_steps:

from pytest_steps import test_steps

def step_a():
    # perform this step ...
    print("step a")
    assert not False  # replace with your logic

def step_b():
    # perform this step
    print("step b")
    assert not False  # replace with your logic

@test_steps(step_a, step_b)
def test_suite_no_shared_results(test_step):
    # Execute the step

You can add a steps_data parameter to your test function if you wish to share a StepsDataHolder object between your steps.

import pytest
from pytest_steps import test_steps, StepsDataHolder

def step_a(steps_data):
    # perform this step ...
    print("step a")
    assert not False  # replace with your logic

    # intermediate results can be stored in steps_data
    steps_data.intermediate_a = 'some intermediate result created in step a'

def step_b(steps_data):
    # perform this step, leveraging the previous step's results
    print("step b")

    # you can leverage the results from previous steps... 
    # ... or pytest.skip if not relevant
    if len(steps_data.intermediate_a) < 5:
        pytest.skip("Step b should only be executed if the text is long enough")

    new_text = steps_data.intermediate_a + " ... augmented"  
    assert len(new_text) == 56

@test_steps(step_a, step_b)
def test_suite_with_shared_results(test_step, steps_data: StepsDataHolder):

    # Execute the step with access to the steps_data holder

Finally, you can automatically skip or fail a step if another has failed using @depends_on, check in the documentation for details.

(I’m the author of this package by the way 😉 )

Answered By: smarie

Leave a Reply

Your email address will not be published. Required fields are marked *