You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello @shab2908 ,
I think that you might have found an answer to your problem, but just in case:
The dotnet compiler is smart enough to know that Specflow is a test framework and you can use it directly with this command:
dotnet test
If you have problems with it, there's the way Visual Studio offers you:
When you use Specflow with VisualStudio, you have a script file called "runtests.cmd" in your project. When you open it, you can see the commands used to compile and run your tests. If you're not sure of which command you want to use, you can directly execute this script.
In case you're lost in this script, those are the commands called in my case (I just removed the commands that check if there are errors due to a wrong configuration with the PATH):
#build the project
MSBuild.exe "yourProject.csproj"
#go in the packages to use Specflow
cd ..\packages\SpecRun.Runner.*\tools\net45
#execute the tests
SpecRun.exe run --baseFolder "%~dp0\bin\Debug" --log "specrun.log" %2 %3 %4 %5
And here's the Specflow doc to use the test in cmd line:
https://specflow.org/getting-started/#ExecuteAgain
Hope it helps,
Best Regards,
Marc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.