.NET – BDD test framework

We are a Microsoft store with a fairly mature technology stack and very skilled .net resources. We have been using TDD since the beginning and are now entering the BDD field. Our work is based on The agile team provides and uses strong agile practices.

Our final testable products are web, wpf and windows forms.

Test resources have introduced BDD, and hope Learn and use Ruby and Cucumber to perform tests. Developers have some resistance because we prefer to stick to the same technology stack and use Specflow (or similar). The tester’s argument is that it is easier to learn.

< p>I want to make sure that developers and testers are not biased and it is worth introducing another technique.

We have similar settings, we have testers to write and implement the steps behind the solution. Our testers are very happy to use .net and c#. I think if you introduce another technology, you may let the developers in their Tests are not run before submission, and are not responsible for testing when they fail, because debugging it will be very difficult. This means that your build will break more than its work.

Start letting the test It may be good for people to write scenarios and pass them to the developers, and the developers will introduce the feature into the application. Then, they may pair with the developers and implement these scenarios together until they are familiar with it.

We are a Microsoft store with a fairly mature technology stack and very skilled .net resources. We have used TDD since the beginning and are now entering the BDD field. Our work Provided by the agile team, using strong agile practices.

Our final testable products are web, wpf and windows forms.

The testing resources introduce BDD, and Hope to learn and use Ruby and Cucumber to perform tests. Developers have some resistance because we prefer to stick to the same technology stack and use Specflow (or similar). The tester’s argument is that it is easier to learn.

I want to make sure that developers and testers are not biased and it is worth introducing another technique.

We have similar settings, we have testers Write and implement the steps behind the solution. Our testers are very happy to use .net and c#. I think if you introduce another technology, you might let the developers not run the tests before they submit them, and when they fail Do not Responsible for testing, because debugging it will be very difficult. This means that your build will break more than its work.

Starting to let testers write scenarios and pass them to developers may be Very good, developers will introduce this feature into the application. Then, they may pair with developers and implement these solutions together until they are familiar with it.

Leave a Comment

Your email address will not be published.