eK Blog

Get Started With EKWORLD!!

EKWORLD is a Testing platform to Unite Acceptance criteria and tests. It is indented to be used collaboratively by everyone in the software delivery team.

EKWORD is a tool that support Behaviour Driven Development (BDD).

EKWORLD can be used in a way that is right for you.

What is BDD?

BDD stands for Behaviour Driven Development.

Behaviour Driven Development (BDD) is a methodology for developing software through continuous example-based communication between developers, QAs and BAs.

Very popular way of defining BDD, made popular by cucumber is GHERKIN format

What is Gherkin?

Gherkin is a structured natural language that is used by business analysts to specify how they want the system to behave for given scenarios.  

The Gherkin language is simple. This format is designed to be both easily understandable for business stakeholders and easy to automate.

Scenario: Depositing money to a savings account

Given I have a Savings account with 1000.00

And I have a money 500.00 to Deposit

When I Deposit 500.00 to my savings account

Then I should have 1500.00 in my savings account

Why BDD?

In traditional approach of software delivery, users give requirements to business analyst. Business analyst relay their understanding of the user’s requirements to the rest of team. Their understanding need not be what the user’s meant. In some cases, business analyst also goes to the extend of designing the solution, instead of telling the team what is needed. This will lead to solution not using the best technical design, that developer would be used for development. It also does not give tester ability to give feedback earlier in the development cycle of the product.

With Traditional approach team members do not have a common sense of ownership and engagement in the solution, as they work in silos.

On the other hand, BDD is highly collaborative process where Business analysts, developers, and testers work together with the end users to define and specify requirements (also known as features), and team members. The requirements are defined with specific examples as stories and scenarios. It is very efficient, as this process draw ideas from their individual experience and know-how. Testers are involved much earlier in the software delivery cycle.

With BDD team members build up a shared appreciation of the users’ needs, as well as a sense of common ownership and engagement in the solution.

World is digitizing – Seeking Low Friction & immediacy – Customers are seeking “Immediate” Response. Trust is not just earned by keeping their money safe but giving UTILITY – all the “services” to their needs.

The future expectation will be that banks should be able to anticipate their customer’s daily experience and proactively meet their needs – in real-time

“Technology is the “Overarching” mechanism of delivering Utility and Trust”

To deliver this banks needs to create a environment which is continous, automatic, learning itself, reach customers where they are already there.

To know how you can create this environment for your customers Get in touch with us at BFC2019EU, Dublin