#5449 RFE: Extend verbose in testing framework
Closed: wontfix 8 months ago by rcritten. Opened 3 years ago by dkupka.

Currently when test module uses fixtures it's not obvious what parameters was used when the test failed. Of course the information can be after a while found in the test module source code but it's not convenient. Adding information about test, its parameters and result returned possibly in higher verbose level would really help.

ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser210] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser211] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser212] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser213] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser214] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser215] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser216] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser217] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser218] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser219] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser220] PASSED
ipatests/test_xmlrpc/test_stageuser_plugin.py::TestStagedUser::test_create_attr[stageduser221] FAILED

Note: following example do the magic in pytest

@pytest.mark.parametrize("key,val", DEFAULT_CONFIG.items())

But I'm not sure if it is possible to use in current staguser tracker.

Metadata Update from @dkupka:
- Issue assigned to lryznaro
- Issue set to the milestone: FreeIPA 4.5 backlog

2 years ago

Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

8 months ago

Login to comment on this ticket.

Metadata