Grasping through the SW Test Automation Landscape one issue that often arises is the business case for executing a test automation engagement. (Not for typical Unit Tests, those should be part of the development effort; the focus here is Functional Testing and GUI Testing).
Are Peer reviews commonly accepted as a value-added practice among the IT-Community? They should be an essential part of the software development cycle, but are usually neglected due to short development sprints, static code analysis, or …
BDD (Behavior Driven Development) has been a buzz word for quite a while. My question is whether to adopt it or not.
I’m gonna start by describing what you can do using this approach. Using ‘Cucumber’ (http://cukes.info/) to illustrate the picture; which is quite amazing for someone not familiar test automation. Then I’ll raise some questions. Cucumber is a software package used for test automation in BDD, originally written in Ruby but ported to other platforms like Java. The idea behind it is to specify tests on natural language that are subsequently translated into automated tests. Allowing a common ground for Business and Functional teams. First you start with a test case (Feature File). Simply a text file, with some well known keywords. The example bellow is for testing the IKEA search page for e.g. |
|