Test-Along Development (TAD): Unit testing technique
While talking to one of the client stakeholder, I came across this interesting term as Test-Along Development.
Following are two different techniques I came across as common way of writing unit test:
- Test-driven development where we write unit tests first and then write enough code to make unit tests pass
- Write unit tests at the end once you are done with the development.
Both of the above techniques presented enough challenges to the software developers. Some of them are following:
- Test-driven development:
- In agile development, in 2 week sprints, the design took much longer than 2-3 days. Thus, doing test-driven development was found to lead carry-overs for sprint given on site-offshore model of development where communication used to take additional time.
- Lack of knowledge of TDD and associated software development practices
- Writing unit tests towards the end
- Lack of time due to delay in feature/functionality completion
- Inability to do decent test coverage due to attention to various different flows of a use case
So, What is Test-Along Development (TAD)?
Simply speaking, TAD is writing unit tests as you are developing the code. This technique is simpler than TDD. However, this is still challenging. Developers still have to plan about unit tests much earlier and, for that reason, have to understand the requirements more diligently.
![](data:image/svg+xml;charset=utf-8,<svg height="400px" width="250px" xmlns="http://www.w3.org/2000/svg" version="1.1"/>)
Check out my latest book titled as First Principles Thinking: Building winning products using first principles thinking.
- Retrieval Augmented Generation (RAG) & LLM: Examples - February 15, 2025
- How to Setup MEAN App with LangChain.js - February 9, 2025
- Build AI Chatbots for SAAS Using LLMs, RAG, Multi-Agent Frameworks - February 8, 2025
Recent Posts
Retrieval Augmented Generation (RAG) & LLM: Examples
Last updated: 25th Jan, 2025 Have you ever wondered how to seamlessly integrate the vast…
How to Setup MEAN App with LangChain.js
Hey there! As I venture into building agentic MEAN apps with LangChain.js, I wanted to…
Build AI Chatbots for SAAS Using LLMs, RAG, Multi-Agent Frameworks
Software-as-a-Service (SaaS) providers have long relied on traditional chatbot solutions like AWS Lex and Google…
Creating a RAG Application Using LangGraph: Example Code
Retrieval-Augmented Generation (RAG) is an innovative generative AI method that combines retrieval-based search with large…
Building a RAG Application with LangChain: Example Code
The combination of Retrieval-Augmented Generation (RAG) and powerful language models enables the development of sophisticated…
Building an OpenAI Chatbot with LangChain
Have you ever wondered how to use OpenAI APIs to create custom chatbots? With advancements…
View Comments
Are you saying that in TDD *all* unit tests should be written before the code? My understanding of TDD (and the "version" that I practice) is what you're calling TAD. I would never attempt to write a full suite of tests in advance of any code, unless the suite was expressed entirely in pseudo-code.