iljabauer / behave-teamcity Goto Github PK

Hi,

I've been using behave-teamcity and have encountered an issue when an error occurs in a step that is not the last step of the behave feature file.

To correct it, I've locally changed line 53 from:

• error_details = self.current_step.error_message
  to:
• error_details = step_result.error_message

Example Feature fie:

1. Given I create an API request
2. When I get the request
3. Then the http status should be 200

If my error occurred on lines 1 or 2 of my feature file (in the example above), then the step failed teamcity message would not contain the details section, but it did contain the message section, which tells you which step has failed but not why it has failed.

When I changed line 53, as I mentioned above, I did then see the relevant exception I had generated when these occurred in lines 1 or 2 in my feature file.

Thanks,
Jim