Elegant Acceptance Testing in .NET with SpecFlow 

Thankyou Nick Chapsas and Specflow for demystifying the interesting topic of Acceptance Testing in .NET

I didn't knew about Fluent Docker, love it

My team has some usage on specflow as well, ultimate goal is to let someone else write the test, but so far are still maintained by developers themselves. My biggest concern/problem is using of verbal sentence and attempt to map it back to the code implementation is very difficult, especially the system is complex enough. Everyone describe the test/steps slightly differently. Some may think your 'given' should not be written in that way, some may think you can describe your 'when' better. Even the same guy who write the description can describe the same scenario steps in a totally different way later when he come back. This is just an extra layer of human language to code mapping which will never be consistent and will never be standardized and you have to spend a lot of time finding whether the step you want in your mind has been implemented by someone already or not. Now, if you find something similar exist, you still need to check if the implementation is just the one you need or not. If not? Then people tend to define some given-when-then in a similar but slightly different way, to just meet their own need. Why not parameterize it? Yes, it can, but this breaks all existing tests, sometimes even across test scenarios if it is some common steps, and no one will risk to do that.

Hooks line 40 is killing me Nick lol since You have me 'hooked' on 1 dot per line formatting. .Build().Start(); Awesome video as always man!

Great video Nick!

2:13 Lol.. I felt your pain when you complained about the lack of a dark theme. Dark themes for the win. This should be a must for all modern UIs.

Nick, thx for greatest videos. I'm totally in love with BDD, but have some troubles with implementing it in .NET.

Gold

Firstly, excellent video Nick. I was unsure about how the HttpClient is being used, as it seems that before each scenario we are instantiating a new HttpClient. This can be harmful when occupying server ports. This way we guarantee a single instance for all tests?

Hi Nick great video. Could you write something about your path to learning specflow and acceptance tests?

I completely understand the need to test a system from an external / user perspective. But I fail to see the value in all of the prose and the artificial given/when/then separation. It just causes headaches with contexts and passing over values (as opposed to local variables in a unit/integration test). Also, the "features" file is just prose, it tells you nothing about what is actually being executed. It's a glorified comment. Where's the benefit?

I had to pause and stop laughing when the bright screen hits...

Outstanding video.

Great video, thanks for creating! But lines of code are too heavy, integration tests with mocking repository is simpler as for me.

I’m interested in how you would write acceptance test for a GUI application. In my previous company they started a headless version of the app and injected the registered services in the tests, do you think there’s a better approach?

great videos! But watching your API-testing videos I’m always wondering why don’t you use TestClient (which will run a real API in-memory) ?

Unit-tests and E2E testing are much easier and take less time to create new tests

Those port numbers though... 😁

Hi Nick! TOP video! Where Do I found the sources for this video?

So what's the difference compared to end-to-end testing?

In my case not working Ductus cannot find the Dockerfile

Hi Nick do you have the same tutorial available using restsharp?kindly give some guidance on using specflow with restsharp and xunit

Great video, especially the part with docker included. I often hear many terms to describe different layers or scopes for tests such as unit, integration, end to end, regression, functional, behavioral, acceptance. How do you go about reconciling all these or what are the nuisances between some that seem the same?

Hi Nick - I'm also using Rider, and I seem to have a problem with the Selenium ChromeDriver process still running after the tests have finished. I have to kill them manually from the command line before I can run them again. Tested it in VS2022 and it kill the process properly after closing the window. Any ideas?

👍

Thank you for this great video. Would you like please to share you dockerfile with us?

How much does Specflow cost?

Did you created table in gurkin by hand or you use some tool?

I'm not able to run the test scenarios from within the feature file, only from the test explorer. What do I miss?

Hi man. How can i get your fully course about of c# or .net core? Have you any tutorial beginner to the advanced?

Is this example available somewhere?

I know and like Cucumber from the Java world. Now I am working in a C# company and really like to introduce here Specflow. Its efficient, precise and really easy-to-use. One question remains: How can e2e Tests be composed from component tests? E.g. we have different apps (web, win, android) and Specflow Tests for each of these components. Tests are all in one .sln and for each component there is a .csproj: AllTests.sln WebTests.csproj WinTests.csproj AndroidTests.csproj e2eTests.csproj In the e2e.csproj I'd like to call tests from the other projects in order to setup e2e Tests across different components. Is this possible with Specflow?