Skip to main content

Do you need BDD style of system tests ?

BDD was largely introduced as a bridge between domain experts who are usually not technical users and Engineers who are supposedly no domain experts. BDD gives an ability to domain experts to describe application feature in Given, When, Then style and these are then turned in to real application feature by Engineers. All stakeholders have common reference of understanding.
But it does not stop there, there was great value (and probably there is ) seen in writing system tests which follow BDD style. JBehave, Cucumber-JVM come on mind quickly. These APIs also help bridge the gap between technical and not technical user, but the questions we need to ask is -
  • Would you be able to get product specialist write the feature files? If not then you would have two sources of information one written by product specialist (probably in JIRA or another tool) and another feature file written by developer or test engineer
  • Will product specialists ever execute the test?
  • Do you want to introduce an extra layer of steps when you might be the only one working and verifying the tests?
BDD Scenario from Dan North  - 
+Scenario 1: Account is in credit+
Given the account is in credit
And the card is valid
And the dispenser contains cash
When the customer requests cash
Then ensure the account is debited
And ensure cash is dispensed
And ensure the card is returned

Modification from James Basch -
+Scenario 1: Account is in credit+
Given the account is in credit
And the card is valid
And the dispenser contains cash
When the customer requests cash
Then check that the account is debited
And check that cash is dispensed
And check that the card is returned
And check that nothing happens that should n’t happen and everything else happens that should happen for all variations of this scenario and all possible states of the ATM and all possible states of the customer’s account and all possible states of the rest of the database and all possible states of the system as a whole, and anything happening in the cloud that should not matter but might matter.
Source
  • Are you ready to deal with the complexity of information flow when you have to maintain the state from step to step ?
And how do you solve the communication problem if you don't use cucumber? Talk to your stack holders, no amount tools can replace face to face communication. BDD is no guarantee of not doing things wrong and decision is yours.
When I was writing cucumber tests then they became source of truth for manual testing team to assume application works well and in case test fail I would have to fix them. I am not sure if cucumber solves any problem when used in this manner.
Labels:

Comments

Post a Comment

No spam only genuine comments :)

Popular posts from this blog

Return only first or last element from webelements collection

We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" ));   Now we can get the first web element from this collection as -  WebElement firstElement = Iterables. getFirst (webElements,  getDriver().findElement(By. id ( "defaultElement" )));   Herein second argument -   (getDriver().findElement(By. id ( "defaultElement" )))    in the me
2 comments
Read more

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro
Read more

Using xPath to reach parent of an element

Well, I am big fan of css locator my self there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also highlighted in image) Herein first I need to reach div parent (class = 'left couponmainarea
Read more