Automated UI testing in .NET using Playwright and Specflow 

seconded!

Trippled

I like the video, but procedural tests would be easier to hand to someone with less experience or someone who doesn't want to sit through how spec flow works again

Please :)

Absolutely would love to have a video on just playwright!

Yeah it can totally be something you have on while working on the code and turn off during your CI/CD pipeline's configuration

It does indeed and you can export them in multiple ways as well.

I personally do use it both for BDD/ATDD scenarios and also for testing. It takes some time to get the whole team up to speed but once you do, you can benefit greately by having it.

All my code from my videos is available for my patrons

Hello Yevgeniy. Could you please disclose that you are the creator of Atata in your comment, otherwise I will have to remove it, since self-promo without disclosure isn't something I allow in my comment section. Thank you for understanding

Sure, no problem. Updated.

For CI/CD, you don't need to do any SpecFlow manipulation. It is enough that the project has the correct dependencies

What i mean is that if the test scenario has steps which interacts with different pageobject classes. How to we handle such situation in before scenario.?

Hey Christian, what comment are you referring to? Something might have been caught by the spam filter. I don’t delete comments, but rather shadow ban users.

@@nickchapsas got it. Thanks for the clarification. I am going to post it again in this thread and see what happens :)

This was my original comment: Thanks for showing a feature file focusing on the behavior rather than describing the UI implementation. There are so many bad tutorials out there encouraging bad practices for writing feature files. By the way, since you mentioned the page object "pattern," it would be nice to see a video of you talking about an alternative to page objects: the Screenplay pattern. Also, a cherry on the top would be a video where the driver pattern is demonstrated, where the very same feature file and the very same step definition can validate the behavior of the system against different layers, like having one driver implementation for executing against the domain model directly and another driver implementation for the UI. Here is a link to an example from specflow team that demonstrates that, choosing what implementation you want to run your test against driven by tags: docs.specflow.org/projects/specflow/en/latest/Getting-Started/Getting-Started-With-An-Example.html and the source code: github.com/SpecFlowOSS/SpecFlow-Examples/tree/master/ASP.NET-MVC/BookShop

I personally prefer the screenplay pattern and I thought I did mention that I. The video. the problem is that it’s hard to make a video about the tech and also show the screenplay pattern because it is more elaborate and would bloat the video runtime

This is a matter of automation framework design and team experience. Since 4 years we already have 5k+ SpecFlow autotests and there are no issues supporting them all (tests fail rate is no more than 0.1%). Of course PageObject is strictly necessary for projects that size

There seems to be many decent ways of testing web apps lately, but not much for desktop unfortunately. Hopefully someone will reply to your comment and prove me wrong :)

It's been a few years, but i think UIA (Microsoft UI Automation) is still the best option.

Snoop WPF might be helpful too: github.com/snoopwpf/snoopwpf