BDD frameworks (part 1)

published in Agile Methodology, Android Development, Project Management, Tutorials
by Wojciech Szóstak

Programmer, tester, manager, client – mutual understanding between these people is essential for the positive completion of any mobile application programming project. Nobody said it would be easy, but BDD frameworks can help.

At the very beginning of a project, as its contractor, we have to define the requirements of an android app with the client. Each required functionality should be described on the basis of a specific structure: title, description and acceptance criterion.

The description should contain information about its: user,  business value, and effect (what happens after the function is performed).

Acceptance criterion is a defined list of steps that must be taken to achieve the desired goal.

Behavior driven testing

To determine that a feature meets the agreed upon acceptance criteria, we must test it. This is where the team often encounters communication barriers on the line: tester-developer or manager-client.

Non-technical people understand the data specified in the test by the programmers differently. In relation to that, they are often unable to check what a given test performs and whether it meets the criteria described in the requirements. Behavior-Driven Development will come to our aid.

In the first part of the article, “BDD frameworks”, I will briefly describe the main assumptions of BDD as the sections following describe selected User Interface testing frameworks and Unit testing frameworks.

What is Behavior-Driven Development?

BDD is a software development process created in 2003 on the basis of TDD. Its main task is to describe the behavior of a system from the perspective of its users. With BDD testing tools we can test application views or perform unit tests, among other things.

BDD development

The main rules of Behavior-Driven Development are as follows:

  • The language in which we describe user behavior needs to be natural (understandable to non-technical users)
  • A feature must be found in each test (i.e., the title and description of the feature, information regarding what function it is to perform as in the requirements).
  • Each test also has a scenario (i.e., steps of acceptance, a description of the business situation as in the requirements)

In the description of the system behavior 3 keywords are used:

  • Given– context, scenario
  • When– behavior, action
  • Then– result

Practical example of “Behavior Driven Development Testing”

Feature: Login feature

    Scenario: As a valid user I can log into my app
      When I press "Login"
      Then I see "Welcome to the coolest app ever"

After learning the main assumptions of BDD we can move on.

See the following articles:


You can find the source code on my GitHub.


 

Wojciech Szóstak Mobile Developer

Wojtek is a mobile developer at Zaven. He mostly works on android apps and enhances his knowledge about software testing (like BDD). In his spare time, Wojtek enjoys martial arts - he exercises several times a week!

Popular posts

3D Touch Quick Actions Tutorial

3D Touch Quick Actions Tutorial

Did you know that the iPhone is able to detect different levels of touch depending on how hard you press? This is all thanks to 3D Touch! Check out how to add 3D Touch quick actions to your iOS apps.

Read more
BDD frameworks (part 3)

BDD frameworks (part 3)

In this series of articles, I am presenting selected BDD testing tools. In this part, I will talk about Spock – a unit testing framework.

Read more
BDD frameworks (part 2)

BDD frameworks (part 2)

In this series of articles, you can learn how to use automated software testing with Behavior-Driven Development. In part 1, I described the main assumptions of the process. Now it is time for BDD testing tools.

Read more
Mobile Apps

Get your mobile app in 3 easy steps!

1

Spec out

with the help of our
business analyst

2

Develop

design, implement
and test, repeat!

3

Publish

get your app out
to the stores


back to top