A Test Automation Blog

You now have this beautifull generated test automation suite and you want to adjust it to your needs, but have no clue where to start. Don't worry, because that is exactly what we're going to cover in the next couple of posts. In this post we'll add a new scenario, make some small adjustments to a step, add a new step and run only that one test to check the results. Cucumber Let's start with a test run with Cucumber. Navigate to the folder in which the tests are stored. So in this case in ` C:\TA\testproject `. In this folder type ` cucumber ` and hit the enter key to run all tests from your generated test suite. But you can also run a limited set of tests. To do so, you should make use of tags in your scenario's . To run only one test you can run it like this ` cucumber -t @whatever `. It will now only run tests that are matching this specific tag and ignore all others.  Add a scenario and run it Let's start with adding a new scenario. For example ...

All installations went well so by now you most likely can't wait to start with test automation. And in the next blog post we will, I promise. But I first want to teach you some handy things, give you some background knowledge to you can do it pretty much correct from the beginning. Editors It is entirely up to you which editor you use. But some have a few nifty tricks. When I started a little more over a year ago with test automation I just went with Notepad ++ . I liked the editor, I knew the editor so it was easy for me to use and to start. A friend of mine has become a fan of RubyMine   which is awesome to use since it's build for this purpose, but not free. Recently I found another editor that is free that looks promising and works very nice, Visual Studio Code . Again, I have my favorite, you might have yours, just use whatever you like most, it really does not matter. IRB If you read my previous blog post you might have noticed we already used it. But why do ...