Hot answers tagged bdd
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 ...
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 ...
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.
This shows how. "TestNG is used to enable parallel execution on runner level"
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 ...
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 ...
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 ...
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).
Fixed the issue by removing '/' before the 'src'
Only top voted, non community-wiki answers of a minimum length are eligible