Closed shivahari closed 1 month ago
Please ignore the failed Codacy Static Analysis
check, it complains about the test_obj
fixture being too complex. We will be fixing it in https://github.com/qxf2/qxf2-page-object-model/issues/471
@rohandudam @Sravanti25
@rohandudam @sravantit25 I have moved the prettytable_object
from integrations/reporting_tools
to core_helpers
and I have created a module - custom_pytest_plugins
and added it to core_helpers
, I moved the CustomTerminalReporter
object from conftest
module to custom_pytest_plugins
.
@shivahari Changes looks good. I ran tests for both positive and negative scenarios. I noticed failure summary is not included in test logs. Can we add it as part of test logs also? If yes, you can take call to make changes as part of this PR or you want to open new one. I am approving PR as of now.
@shivahari Changes looks good. I ran tests for both positive and negative scenarios. I noticed failure summary is not included in test logs. Can we add it as part of test logs also? If yes, you can take call to make changes as part of this PR or you want to open new one. I am approving PR as of now.
The failure summary will not be present in the failure log just like how pytest
logs are not printed in the test logs currently. This is a pytest
plugin change.
The summary will appear on the log when we integrate our logging object with pytest
.
Integrated
prettytable
failure summary to the framework as apytest
plugin. TheTerminalReporter
pytest plugin is overwritten with aCustomTerminalReported
object to print the table summary. Theprettytable
is used only when there is a failure.Changes tracked in the PR:
pytest
plugin to print the failures in a table using prettytableconftest.py
file to get the failed scenarios from test objects and pass them on to thetestreporter
pluginintegrations/reporting_tools/prettytable_object.py
module to configure the table used to print the test failure summary