Skip to content

MINIFICPP-2739 Add test scenario info to behave logs#2129

Open
lordgamez wants to merge 2 commits intoapache:mainfrom
lordgamez:MINIFICPP-2739
Open

MINIFICPP-2739 Add test scenario info to behave logs#2129
lordgamez wants to merge 2 commits intoapache:mainfrom
lordgamez:MINIFICPP-2739

Conversation

@lordgamez
Copy link
Contributor

Behave only starts log capture after before_scenario hook is finished, so any log entries especially scenario information are lost. Add scenario information as a separate file next to the scenario.log file to be able to identify which test scenario the log file belongs to.

https://issues.apache.org/jira/browse/MINIFICPP-2739


Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced
    in the commit message?

  • Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

  • Has your PR been rebased against the latest commit within the target branch (typically main)?

  • Is your initial contribution a single, squashed commit?

For code changes:

  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • If applicable, have you updated the LICENSE file?
  • If applicable, have you updated the NOTICE file?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

Behave only starts log capture after before_scenario hook is finished,
so any log entries especially scenario information are lost. Add
scenario information as a separate file next to the scenario.log file to
be able to identify which test scenario the log file belongs to.
@martinzink martinzink added ready-to-merge low-impact Test only or trivial change that's most likely not gonna introduce any new bugs labels Mar 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

low-impact Test only or trivial change that's most likely not gonna introduce any new bugs ready-to-merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants