search

SpecFlowOSS / SpecFlow

#1 .NET BDD Framework. SpecFlow automates your testing & works with your existing code. Find Bugs before they happen. Behavior Driven Development helps developers, testers, and business representatives to get a better understanding of their collaboration
https://www.specflow.org/
Other
2.22k stars 752 forks source link

Documentation request: #2643

Closed Roganik closed 1 year ago

Roganik commented 1 year ago

Product:
[x] SpecFlow+ Runner (NUnit3)

https://github.com/SpecFlowOSS/SpecFlow/blob/master/docs/Integrations/NUnit.md

What is missing:

Is there a documentation on how test name is constructed? (and is it possible to override it?) When using NUnit.ConsoleRunner

Context

In some cases there is a nested folder structure and long scenario description. And when I run such tests for CI, test names become very long.

Is there a way to override test name construction? I'd love to shorten it somehow.

SabotageAndi commented 1 year ago

No, there is no way to adjust the test name construction. Part is done by NUnit, part is done by the attributes we use and generate and part is done how we generate the code-behind files. Nothing can be adjusted.

github-actions[bot] commented 1 year ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.