Hot answers tagged

5

The TDD cycle is more a development cycle for a developer, to quote James Shore, The Art of Agile, Test-Driven Development chapter: Programmers new to TDD are often surprised at how small each increment can be. Although you might think that only beginners need to work in small steps, my experience is the reverse: the more TDD experience you have, ...


3

If developers also write unit tests, then what's the point of having special testers in our team and should we replace testers with developers? Unit testing is not the only kind of automated testing. Integration tests, performance tests, scalability tests, and fault tolerance tests are all examples of automated tests that are not unit tests and that a ...


3

I'd plan it this way: The specific tests that are written 'before the code' are unit tests that are written by developers just before they write the actual code. It should only take 5-20 minutes to write a simple test. The test is written, the code is written for it and then the test is changed or the next test is written and then more unit level code is ...


3

This shows how. "TestNG is used to enable parallel execution on runner level"


3

This looks fine. BDD feature files is meant to be at a level to give useful information to product folks. In each step you can call lower level steps if you want to give more specific information (or more reusable actions) For this one for example Given I am signed in It might just call within it // enter the username GivenIEnterInTheField(string ...


3

I would recommend doing both approaches, for different purposes. Given / When / Then is good for testing communication. This format brings assurance that what you are testing is what the business owner / requirements writer intended. The bugs mainly caught by these tests, IME, are ones where the business owner intended X and the dev did Y. Often, these ...


2

The more detailed the test case, the more time you will spend on revisions as the software evolves. The less detailed the test case, the more you are leaving it up to your testers to read between the lines. Maybe you should try it both ways and see how it goes.


2

This is my first try to setup Behat Magetest for Magento on my MacOS - my tests run quite well and I want to share my experience. First of all you should download MAMP Pro and Magento, if you did not do it already. It works without MAMP too - but that is how I did it - so feel free to work without MAMP. My final tests are based on the sample data provided ...


2

I use BDD Frameworks commonly as QA Automation using Cucumber4JVM and Specflow. If your developers are writing the automation framework and your business is writing out the specs than that is amazing for you. I would start by reviewing over the Specs with the business, try and make certain that as many (reasonable) specs are covered. I would also review ...


2

Unit test should be written by developers. Unit test are very close to the core code and developers have intimate knowledge of how units should work. testers are usually more removed from the deep innards of the core code and they will not be ass effective writing unit tests as core developers are. Acceptance/integration/end-to-end test do not require this ...


1

Let me answer your queries in a different way i.e. not by looking at the number of testers and developers and how to utilise them during the initial phases of development cycle. TDD and TFD tries to emphasise on a very important aspect of SDLC which in the long term helps in reducing testing costs and helps to launch a product on time if not sooner. ...


1

In my project I created common step definition file with common method like login, logout, selecting checkbox(s), setting value in input fields, taking screenshot, selecting value in dropdown, selecting option in radio button group etc. and created separate step definition files for feature specific steps. And I was easily able to manage complete testsuite ...


1

From my experience at work a feature is a user story. There's a 1:1 relationship between a feature (as in Specflow) and a user story (as in BDD).



Only top voted, non community-wiki answers of a minimum length are eligible