I have set up the TeamcityFormatter as explained here in my project. When I run the behave tests, I get console outputs of the type
##teamcity[testFinished timestamp='2022-06-23T13:26:43.701' duration='95' name='When the Trainer starts a training using this bundle ID']
##teamcity[testStarted timestamp='2022-06-23T13:26:43.702' name='Then the training starts']
##teamcity[testFinished timestamp='2022-06-23T13:26:43.702' duration='0' name='Then the training starts']
##teamcity[testStarted timestamp='2022-06-23T13:26:43.702' name='And the Trainer gets a model ID']
etc.
Of course, this results in a test report that doesn't meet my requirements: every gherkin step is considered a test on its own. I want to setup the TeamcityFormatter in such a way that each scenario is considered as test. How do I achieve that? It's difficult to find documentation on this. The workaround is to configure behave in such a way that it outputs the junit reports and to activate the TeamCity XML Report Processing feature.
I have set up the
TeamcityFormatteras explained here in my project. When I run the behave tests, I get console outputs of the typeetc.
Of course, this results in a test report that doesn't meet my requirements: every gherkin step is considered a test on its own. I want to setup the
TeamcityFormatterin such a way that each scenario is considered as test. How do I achieve that? It's difficult to find documentation on this. The workaround is to configure behave in such a way that it outputs the junit reports and to activate the TeamCity XML Report Processing feature.