Automatic Testing - White Label Coders
White Label Coders  /  Blog  /  Automatic Testing

Category: Software Engineering

Automatic Testing

automating testing
3 min read

Creating automated tests is a very important element of the software development process.

This approach to creating tests utilizes TDD and BDD methodologies

Both TDD and BDD describe the same model of functionality that was implemented.

Each functionality is created according to a specific scheme consisting of three steps:

1) Creating a test (or scenario) for a desired functionality which initially has a negative result (due to the lack of code implemented);

2) Implementing a desired functionality, by writing code which fulfills the needs of the initial test and then passes it.

3) Refactoring the earlier code.

So what are TDD and BDD and what is the difference between them?

TDD (Test Driven Development) – as the name suggests, this is an approach which describes testing-based programming. In this case, we’re talking about unit tests. We test and implement minor functionalities, which are responsible for individual tasks.

BDD (Behavior Driven Development) – in this case, is functionality based on specific scenarios. The scenarios represent a set of requirements that must be met in order for a given functionality to be considered ready.

In the case of behavioral tests, we test a part of the application in relation to the entire system, whereas unit tests only verify individual tasks.

So how do you apply this knowledge in practice?

The most important aspect of creating any software is the development of User Stories. User Stories, in a literal translation, is the user’s story. Maybe it sounds a bit funny, but that is in fact just what it is. When the required standards are followed, the resulting User Story reveals the client’s functional requirements. As we all know, clients often “don’t know what I want,” or “know,” but can’t explain it.

This is where a User Story comes in.  An important element is documenting the entire ‘history’ of functionality. However, as in every engineering project, this has to be done in accordance with a strict set procedure. Since examples work best, here’s a scenario for ordering a product from an online store:

As a logged in user

When I place an order consisting of products: a TV set and a vending machine

Then a new order will appear in the database with a total price of PLN 2,000.

The User Story, as seen above, specifies: who performs the given action, what the action is and what should happen, confirming that the task was carried out. A well prepared User Story is just a scenario that will be used in the behavioral test in the BDD approach. The keywords in bold are significant. They define the standards – who, what and why the action was taken.

The task of the behavioral test is to verify whether the entire scenario has been implemented correctly. The test will only be ‘passed’ when all the stages have been carried out correctly. If any of the steps ‘fail’ the test, the entire test has been failed.

Unit tests are complementary to behavioral tests. They examine the processes which occur  during the scenario, in great detail. So, in the above example, if a behavioral test is applied and it checks whether the user is logged in, the order was created and the price is correct; then a unit test can be applied to check a specific scenario, such as, the calculation of the gross price of the product.

It’s important to come away with the functionality quickly, so that the general concept of the project can be identified and the details can be filtered out. It’s important to remember that the development of good code is based on good processes (TDD and BDD) and begins with the client’s needs analysis.

A well told User Story allows for the thorough development of behavioral testing, and specific tasks for unit testing. This, in turn, drives the development of the most bulletproof software. Of course, you can’t forget the need for good programming practices like SOLID and KISS (as I mentioned in a previous article), because only ‘good’ code is ready for automatic testing.

You can read more about automatic testing

Good luck!


Upper-mid PHP Developer / Frontend & Backend

Professional in full-stack web development. His experience covers building websites, online shops, APIs and maintaining them. Driven by solution design and user’s satisfaction, supported by solid interpersonal and management skills make a robust, all-round developer who can take on the impossible. Strongly focused on quality and best practices, fan of SOLID and KISS approach, experienced with automated testing.

Related Articles
Check related articles
Rewriting IT Systems from Scratch
5 Reasons Why It Is Not Worth Rewriting IT Systems From Scratch

When clients are seeking IT services, they are usually in one of two situations: They have a new business idea based on an IT system, or they currently have this type of business and the system is seriously suffering. 

Read more
Code Reviews - Putting the “Team” in Teamwork

The quality of the code defines the final effect of the completed project for the client. Regardless of the complexity of the project, software development can be divided into specific pieces of functionality, which ultimately make up the whole - business effect recommended by the client: online store, website, order management platform, game creation system, application ...

Read more
Why TypeScript
Why TypeScript?

Node JS is great for api development, we have used it for ages. We also have great web frameworks like express and koa, nice orms like sequelize, bookshelf, objection and mongoos, and we have a lot of other libraries and plugins that we love to use.

Read more
Schema mockups and microdata
Schema mockups and microdata - how they affect SEO?

You've probably heard about HTML tags and structured data many times. If you are a web developer, you should know them well.

Read more
Anmalysis of software development project
Analysis of the Project - Necessary Evil or Mark of Quality

The client urgently needs to know the project budget during the first contact with a team of specialists to even decide initially whether he can afford it. Unfortunately, to accurately estimate the project budget, analysis of project parameters needs to be gained from a client needs analysis.

Read more
delighted programmer with glasses using computer
Let’s talk about your WordPress project!

Do you have an exciting strategic project coming up that you would like to talk about?