How to ignore python UserWarning in pytest?












1















I am using openpyxl for parsing .xlsm files, and pytest for testing.



When I open a file, I get the:

OpenPyxl -> UserWarning: Data Validation extension is not supported and will be removed



That is not really a problem bcs. program works and I can't change the .xlsm file to fix that.



But...
When I run pytest with something like:



def test_wrong_file_format():  
assert check_excel(open_excel('file.xlsm')) == True


I will get the warning i mentioned altought check_excel(open_excel('file.xlsm')) returns True and the test should suceed...



Is there a nice way to tell the pytest that "It's not a bug it's a feature" and tests should pass even when they get this warning?



Is there other way than using something like:



with pytest.warns(UserWarning):
warnings.warn("my warning", UserWarning)


Thank you,

Tom










share|improve this question























  • pytest -W ignore::UserWarning. Or persist it in pytest.cfg to not to enter it each time: filterwarnings = ignore::UserWarning.

    – hoefling
    Nov 22 '18 at 16:39
















1















I am using openpyxl for parsing .xlsm files, and pytest for testing.



When I open a file, I get the:

OpenPyxl -> UserWarning: Data Validation extension is not supported and will be removed



That is not really a problem bcs. program works and I can't change the .xlsm file to fix that.



But...
When I run pytest with something like:



def test_wrong_file_format():  
assert check_excel(open_excel('file.xlsm')) == True


I will get the warning i mentioned altought check_excel(open_excel('file.xlsm')) returns True and the test should suceed...



Is there a nice way to tell the pytest that "It's not a bug it's a feature" and tests should pass even when they get this warning?



Is there other way than using something like:



with pytest.warns(UserWarning):
warnings.warn("my warning", UserWarning)


Thank you,

Tom










share|improve this question























  • pytest -W ignore::UserWarning. Or persist it in pytest.cfg to not to enter it each time: filterwarnings = ignore::UserWarning.

    – hoefling
    Nov 22 '18 at 16:39














1












1








1








I am using openpyxl for parsing .xlsm files, and pytest for testing.



When I open a file, I get the:

OpenPyxl -> UserWarning: Data Validation extension is not supported and will be removed



That is not really a problem bcs. program works and I can't change the .xlsm file to fix that.



But...
When I run pytest with something like:



def test_wrong_file_format():  
assert check_excel(open_excel('file.xlsm')) == True


I will get the warning i mentioned altought check_excel(open_excel('file.xlsm')) returns True and the test should suceed...



Is there a nice way to tell the pytest that "It's not a bug it's a feature" and tests should pass even when they get this warning?



Is there other way than using something like:



with pytest.warns(UserWarning):
warnings.warn("my warning", UserWarning)


Thank you,

Tom










share|improve this question














I am using openpyxl for parsing .xlsm files, and pytest for testing.



When I open a file, I get the:

OpenPyxl -> UserWarning: Data Validation extension is not supported and will be removed



That is not really a problem bcs. program works and I can't change the .xlsm file to fix that.



But...
When I run pytest with something like:



def test_wrong_file_format():  
assert check_excel(open_excel('file.xlsm')) == True


I will get the warning i mentioned altought check_excel(open_excel('file.xlsm')) returns True and the test should suceed...



Is there a nice way to tell the pytest that "It's not a bug it's a feature" and tests should pass even when they get this warning?



Is there other way than using something like:



with pytest.warns(UserWarning):
warnings.warn("my warning", UserWarning)


Thank you,

Tom







python pytest openpyxl user-warning






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 16:16









Tom91Tom91

83




83













  • pytest -W ignore::UserWarning. Or persist it in pytest.cfg to not to enter it each time: filterwarnings = ignore::UserWarning.

    – hoefling
    Nov 22 '18 at 16:39



















  • pytest -W ignore::UserWarning. Or persist it in pytest.cfg to not to enter it each time: filterwarnings = ignore::UserWarning.

    – hoefling
    Nov 22 '18 at 16:39

















pytest -W ignore::UserWarning. Or persist it in pytest.cfg to not to enter it each time: filterwarnings = ignore::UserWarning.

– hoefling
Nov 22 '18 at 16:39





pytest -W ignore::UserWarning. Or persist it in pytest.cfg to not to enter it each time: filterwarnings = ignore::UserWarning.

– hoefling
Nov 22 '18 at 16:39












1 Answer
1






active

oldest

votes


















1














According to official documentation (pytest)
@pytest.mark.filterwarnings - is the right approach.
Just choose correct param, for example:



@pytest.mark.filterwarnings('ignore:UserWarning');





share|improve this answer
























  • Thank you, it works. the correct syntax is: @pytest.mark.filterwarnings('ignore::UserWarning')

    – Tom91
    Nov 26 '18 at 9:29











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434877%2fhow-to-ignore-python-userwarning-in-pytest%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














According to official documentation (pytest)
@pytest.mark.filterwarnings - is the right approach.
Just choose correct param, for example:



@pytest.mark.filterwarnings('ignore:UserWarning');





share|improve this answer
























  • Thank you, it works. the correct syntax is: @pytest.mark.filterwarnings('ignore::UserWarning')

    – Tom91
    Nov 26 '18 at 9:29
















1














According to official documentation (pytest)
@pytest.mark.filterwarnings - is the right approach.
Just choose correct param, for example:



@pytest.mark.filterwarnings('ignore:UserWarning');





share|improve this answer
























  • Thank you, it works. the correct syntax is: @pytest.mark.filterwarnings('ignore::UserWarning')

    – Tom91
    Nov 26 '18 at 9:29














1












1








1







According to official documentation (pytest)
@pytest.mark.filterwarnings - is the right approach.
Just choose correct param, for example:



@pytest.mark.filterwarnings('ignore:UserWarning');





share|improve this answer













According to official documentation (pytest)
@pytest.mark.filterwarnings - is the right approach.
Just choose correct param, for example:



@pytest.mark.filterwarnings('ignore:UserWarning');






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 22 '18 at 17:13









AlekseyAleksey

93979




93979













  • Thank you, it works. the correct syntax is: @pytest.mark.filterwarnings('ignore::UserWarning')

    – Tom91
    Nov 26 '18 at 9:29



















  • Thank you, it works. the correct syntax is: @pytest.mark.filterwarnings('ignore::UserWarning')

    – Tom91
    Nov 26 '18 at 9:29

















Thank you, it works. the correct syntax is: @pytest.mark.filterwarnings('ignore::UserWarning')

– Tom91
Nov 26 '18 at 9:29





Thank you, it works. the correct syntax is: @pytest.mark.filterwarnings('ignore::UserWarning')

– Tom91
Nov 26 '18 at 9:29




















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434877%2fhow-to-ignore-python-userwarning-in-pytest%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

RAC Tourist Trophy