Python Behave integration. Step and Scenario based implementation.
Required packages:
behave==1.2.6
or relevant versionpytest-reportportal
Is responsible for Scenario or Step based logging
example: >behave -D step_based=True
in this case Step based logging will be applied.
Note: Scenario based logging applied by default
Is responsible for logging into report portal. If it is disabled then no loggin will be into report portal.
example: >behave -D rp_enable=True
Note: Report portal logging enabled by default
In your behave.ini
file you will have to add [report_portal]
block
rp_endpoint =
report_portal_urlrp_project =
your report portal project namerp_token =
your UUID (can found in your profile of Report portal)rp_launch_name =
'Your default launch name'rp_launch_description =
'Your default launcher description'
Note: behave.local.ini
file is for local using. Reading from it is 1st in queue. If it does not exist, then behave.ini
wil be applied