Is this wrong xfail output from pytest
I'm new to pytest and experimenting with using the pytest.xfail decorator.
My question is whether the output I get is too much/wrong and therefore indicates that I am doing something wrong. The reason I ask is that it is way more that I have seen in other examples. The final summary does show correctly as 1 xfailed in 2.61 seconds.
I'm testing a Flask app which should return Hello World on a get to /:
@pytest.fixture
def client():
client = application.app.test_client()
yield client
@pytest.mark.xfail(reason='should fail')
def test_hello_world(client):
r = client.get('/')
assert r.get_json() == '12Hello World'
The output is
test_application.py x
client = <FlaskClient <Flask 'application'>>
@pytest.mark.xfail(reason='should fail')
def test_hello_world(client):
r = client.get('/')
> assert r.get_json() == '12Hello World'
E AssertionError: assert 'Hello World' == '12Hello World'
E - Hello World
E + 12Hello World
E ? ++
test_application.py:30: AssertionError
[100%]
========================== 1 xfailed in 2.61 seconds ==========================
Should it really show the error and everything? Other examples I have seen just show the x indicating an expected failed test. Also, it does not show the reason which also surprises me. I do not have the -v (verbose) argument on when running. I run the tests in Pycharm.
python pytest
asked Nov 14 '18 at 10:15
Kaspar HKaspar H
276
add a comment |
I'm new to pytest and experimenting with using the pytest.xfail decorator.
My question is whether the output I get is too much/wrong and therefore indicates that I am doing something wrong. The reason I ask is that it is way more that I have seen in other examples. The final summary does show correctly as 1 xfailed in 2.61 seconds.
I'm testing a Flask app which should return Hello World on a get to /:
@pytest.fixture
def client():
client = application.app.test_client()
yield client
@pytest.mark.xfail(reason='should fail')
def test_hello_world(client):
r = client.get('/')
assert r.get_json() == '12Hello World'
The output is
test_application.py x
client = <FlaskClient <Flask 'application'>>
@pytest.mark.xfail(reason='should fail')
def test_hello_world(client):
r = client.get('/')
> assert r.get_json() == '12Hello World'
E AssertionError: assert 'Hello World' == '12Hello World'
E - Hello World
E + 12Hello World
E ? ++
test_application.py:30: AssertionError
[100%]
========================== 1 xfailed in 2.61 seconds ==========================
Should it really show the error and everything? Other examples I have seen just show the x indicating an expected failed test. Also, it does not show the reason which also surprises me. I do not have the -v (verbose) argument on when running. I run the tests in Pycharm.
python pytest
asked Nov 14 '18 at 10:15
Kaspar HKaspar H
276
The additional output must be from Pycharm; try running the tests from command line, you shouldn't get any asserts printed.
– hoefling
Nov 14 '18 at 15:42
add a comment |
I'm new to pytest and experimenting with using the pytest.xfail decorator.
My question is whether the output I get is too much/wrong and therefore indicates that I am doing something wrong. The reason I ask is that it is way more that I have seen in other examples. The final summary does show correctly as 1 xfailed in 2.61 seconds.
I'm testing a Flask app which should return Hello World on a get to /:
@pytest.fixture
def client():
client = application.app.test_client()
yield client
@pytest.mark.xfail(reason='should fail')
def test_hello_world(client):
r = client.get('/')
assert r.get_json() == '12Hello World'
The output is
test_application.py x
client = <FlaskClient <Flask 'application'>>
@pytest.mark.xfail(reason='should fail')
def test_hello_world(client):
r = client.get('/')
> assert r.get_json() == '12Hello World'
E AssertionError: assert 'Hello World' == '12Hello World'
E - Hello World
E + 12Hello World
E ? ++
test_application.py:30: AssertionError
[100%]
========================== 1 xfailed in 2.61 seconds ==========================
Should it really show the error and everything? Other examples I have seen just show the x indicating an expected failed test. Also, it does not show the reason which also surprises me. I do not have the -v (verbose) argument on when running. I run the tests in Pycharm.
python pytest
asked Nov 14 '18 at 10:15
Kaspar HKaspar H
276
I'm new to pytest and experimenting with using the pytest.xfail decorator.
My question is whether the output I get is too much/wrong and therefore indicates that I am doing something wrong. The reason I ask is that it is way more that I have seen in other examples. The final summary does show correctly as 1 xfailed in 2.61 seconds.
I'm testing a Flask app which should return Hello World on a get to /:
@pytest.fixture
def client():
client = application.app.test_client()
yield client
@pytest.mark.xfail(reason='should fail')
def test_hello_world(client):
r = client.get('/')
assert r.get_json() == '12Hello World'
The output is
test_application.py x
client = <FlaskClient <Flask 'application'>>
@pytest.mark.xfail(reason='should fail')
def test_hello_world(client):
r = client.get('/')
> assert r.get_json() == '12Hello World'
E AssertionError: assert 'Hello World' == '12Hello World'
E - Hello World
E + 12Hello World
E ? ++
test_application.py:30: AssertionError
[100%]
========================== 1 xfailed in 2.61 seconds ==========================
Should it really show the error and everything? Other examples I have seen just show the x indicating an expected failed test. Also, it does not show the reason which also surprises me. I do not have the -v (verbose) argument on when running. I run the tests in Pycharm.
python pytest
python pytest
asked Nov 14 '18 at 10:15
Kaspar HKaspar H
276
asked Nov 14 '18 at 10:15
Kaspar HKaspar H
276
asked Nov 14 '18 at 10:15
Kaspar HKaspar H
276
asked Nov 14 '18 at 10:15
Kaspar HKaspar H
276
asked Nov 14 '18 at 10:15
Kaspar HKaspar H
276
276
The additional output must be from Pycharm; try running the tests from command line, you shouldn't get any asserts printed.
– hoefling
Nov 14 '18 at 15:42
add a comment |
The additional output must be from Pycharm; try running the tests from command line, you shouldn't get any asserts printed.
– hoefling
Nov 14 '18 at 15:42
The additional output must be from Pycharm; try running the tests from command line, you shouldn't get any asserts printed.
– hoefling
Nov 14 '18 at 15:42
The additional output must be from Pycharm; try running the tests from command line, you shouldn't get any asserts printed.
– hoefling
Nov 14 '18 at 15:42
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53297745%2fis-this-wrong-xfail-output-from-pytest%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53297745%2fis-this-wrong-xfail-output-from-pytest%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The additional output must be from Pycharm; try running the tests from command line, you shouldn't get any asserts printed.
– hoefling
Nov 14 '18 at 15:42