-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scenario description is missed #25
Comments
@yurii-hunter I removed it because it seemed like a solution for very specific case. I don't think that it should be a default behavior since it duplicates text of all steps in test item description. The same text can be found under test item as logs. It should rather be implemented in your solution using extension points (events) - collect step text in BeforeStepStarted event and update description in BeforeScenarioFinished. I can add scenario and feature context properties to EventArgs classes so it will be easier for you to get access to them from static event handlers. @nvborisenko What do you think about it? |
@aliaksandrbasau sounds reasonable. So, if it is by design - I'm ok. I will implement it on my own in a work project. Just wanted to make sure |
@yurii-hunter Please let me know if you need scenario and feature context properties in EventArgs classes. |
Let me reopen this issue. Definitely we don't want to see steps as scenario description. The future release of specflow will contain some description of scenarios (SpecFlowOSS/SpecFlow#1078). I am not sure what exactly it will contain, but let us to follow official way. |
Done in v1.2.4. Actual description is empty :) |
Initially, we had a description for a scenario in report portal for the SpecFlow client which contained scenario steps, for now, it is missed. The change was made in the scope of this PR Initial Parallel Execution support by @aliaksandrbasau, and variable CurrentScenarioDescription is marked as Obsolete. I would like to clarify is it an issue or just the decision to get rid of this functionality?
The text was updated successfully, but these errors were encountered: