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.

Comments

Popular posts from this blog

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

Security Testing and Selenium

I have come across many articles which talk of carrying out security testing with selenium however I found it very cumbersome to set up such tests. This is what this tutorial is going to make easy for you. It cover. My next Security Testing and Selenium YouTube video covers following - Importance of having security testing on CI What is dynamic application security testing Recommended tools from https://owasp.org/www-community/Vulnerability_Scanning_Tools What is https://owasp.org/ ?   Using https://www.zaproxy.org/    Project setup  <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap-clientapi </artifactId> <version> 1.9.0 </version> </dependency> <dependency> <groupId> org.zaproxy </groupId> <artifactId> zap </artifactId> <version> 2.10.0 </version> </dependency> Start ZAP daemom (headless) mode  ./zap.sh -daemon -host 127.0.0.1 -port 8080 -config api.addrs.a

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