Test-Driven Development

Bailey Fraser

09 Dec 2024 — 1 min read

What is Test Driven Development?

Test Driven Development (TDD) is a process for building software that helps to guide software development by focusing on testing. It involves writing tests before writing any code so that you are then writing code to make the test pass. It ensures that you know what needs to be done before you start and helps to keep you on track as you are only focusing on implementing one piece of functionality.

The steps of TDD are:

1. List all functionality for new feature
2. Write a test for one of the new pieces of functionality
3. Run all tests - the new one should fail
4. Write the simplest code to pass the test
5. Run all tests - they should all pass
6. Refactor as needed whilst continuing to run tests
Repeat Steps 2 - 6 until all pieces of functionality have been implemented into tests.

Following these steps ensures that a program is built piece by piece with each piece being well tested so that if new code breaks any older parts of the program you will know as soon as you run a test and then you don’t have to spend as much time debugging to find out if new code has caused old tests to fail.

Loose Coupled Architecture

Loosely Coupled Architecture is where individual components of an application are built independently from each other. Whilst generally being a slower approach to development, it does have a number of benefits, especially as an application or system scales. Benefits Decreased Maintenance Complexity Improves maintainability by reducing the impact that changes

Event Driven Architecture

Event-Driven Architecture is a programming design principle where a program's functionality is triggered by incoming events; for example sending a purchase order email after a customer places an order. How does Event Driven Architecture work? Event-driven architecture (EDA) is a software design pattern used to help build systems

SOLID

SOLID programming design principles help to develop systems that are more scalable, robust and flexible which can increase the maintainability and reduce technical debt. What is SOLID? Solid is an acronym that stands for: * Single Responsibility Principle * Open/Closed Principle * Liskov Substitution Principle * Interface Segregation Principle * Dependency Inversion Principle And

CV

I am a software engineer with 3 years of experience in the e-commerce sector, contributing to both frontend and backend development using technologies such as HTML, CSS, PHP, and JavaScript. I have a proven track record of collaborating in small teams to solve problems, deliver innovative solutions, and drive significant

What is Test Driven Development?

Read more

Loose Coupled Architecture

Event Driven Architecture

SOLID

CV