Home Programming News Exploring Generative AI

Exploring Generative AI

Exploring Generative AI


TDD with GitHub Copilot

by Paul Sobocinski

Will the arrival of AI coding assistants similar to GitHub Copilot imply that we gained’t want checks? Will TDD grow to be out of date? To reply this, let’s look at two methods TDD helps software program growth: offering good suggestions, and a method to “divide and conquer” when fixing issues.

TDD for good suggestions

Good suggestions is quick and correct. In each regards, nothing beats beginning with a well-written unit take a look at. Not handbook testing, not documentation, not code evaluation, and sure, not even Generative AI. The truth is, LLMs present irrelevant info and even hallucinate. TDD is particularly wanted when utilizing AI coding assistants. For a similar causes we want quick and correct suggestions on the code we write, we want quick and correct suggestions on the code our AI coding assistant writes.

TDD to divide-and-conquer issues

Downside-solving by way of divide-and-conquer implies that smaller issues may be solved earlier than bigger ones. This allows Steady Integration, Trunk-Primarily based Growth, and in the end Steady Supply. However do we actually want all this if AI assistants do the coding for us?

Sure. LLMs hardly ever present the precise performance we want after a single immediate. So iterative growth just isn’t going away but. Additionally, LLMs seem to “elicit reasoning” (see linked examine) once they clear up issues incrementally by way of chain-of-thought prompting. LLM-based AI coding assistants carry out finest once they divide-and-conquer issues, and TDD is how we do this for software program growth.

TDD ideas for GitHub Copilot

At Thoughtworks, we’ve been utilizing GitHub Copilot with TDD because the begin of the yr. Our objective has been to experiment with, consider, and evolve a sequence of efficient practices round use of the device.

0. Getting began

TDD represented as a three-part wheel with 'Getting Started' highlighted in the center

Beginning with a clean take a look at file doesn’t imply beginning with a clean context. We regularly begin from a person story with some tough notes. We additionally discuss by way of a place to begin with our pairing accomplice.

That is all context that Copilot doesn’t “see” till we put it in an open file (e.g. the highest of our take a look at file). Copilot can work with typos, point-form, poor grammar — you title it. However it will possibly’t work with a clean file.

Some examples of beginning context which have labored for us:

  • ASCII artwork mockup
  • Acceptance Standards
  • Guiding Assumptions similar to:
    • “No GUI wanted”
    • “Use Object Oriented Programming” (vs. Practical Programming)

Copilot makes use of open recordsdata for context, so protecting each the take a look at and the implementation file open (e.g. side-by-side) vastly improves Copilot’s code completion capability.

1. Pink

TDD represented as a three-part wheel with the 'Red' portion highlighted on the top left third

We start by writing a descriptive take a look at instance title. The extra descriptive the title, the higher the efficiency of Copilot’s code completion.

We discover {that a} Given-When-Then construction helps in 3 ways. First, it reminds us to supply enterprise context. Second, it permits for Copilot to supply wealthy and expressive naming suggestions for take a look at examples. Third, it reveals Copilot’s “understanding” of the issue from the top-of-file context (described within the prior part).

For instance, if we’re engaged on backend code, and Copilot is code-completing our take a look at instance title to be, “given the person… clicks the purchase button, this tells us that we must always replace the top-of-file context to specify, “assume no GUI” or, “this take a look at suite interfaces with the API endpoints of a Python Flask app”.

Extra “gotchas” to be careful for:

  • Copilot could code-complete a number of checks at a time. These checks are sometimes ineffective (we delete them).
  • As we add extra checks, Copilot will code-complete a number of traces as a substitute of 1 line at-a-time. It is going to usually infer the proper “prepare” and “act” steps from the take a look at names.
    • Right here’s the gotcha: it infers the proper “assert” step much less usually, so we’re particularly cautious right here that the brand new take a look at is accurately failing earlier than transferring onto the “inexperienced” step.

2. Inexperienced

TDD represented as a three-part wheel with the 'Green' portion highlighted on the top right third

Now we’re prepared for Copilot to assist with the implementation. An already present, expressive and readable take a look at suite maximizes Copilot’s potential at this step.

Having mentioned that, Copilot usually fails to take “child steps”. For instance, when including a brand new technique, the “child step” means returning a hard-coded worth that passes the take a look at. To this point, we haven’t been in a position to coax Copilot to take this strategy.

Backfilling checks

As an alternative of taking “child steps”, Copilot jumps forward and gives performance that, whereas usually related, just isn’t but examined. As a workaround, we “backfill” the lacking checks. Whereas this diverges from the usual TDD circulation, we’ve but to see any severe points with our workaround.

Delete and regenerate

For implementation code that wants updating, the best approach to contain Copilot is to delete the implementation and have it regenerate the code from scratch. If this fails, deleting the strategy contents and writing out the step-by-step strategy utilizing code feedback could assist. Failing that, one of the simplest ways ahead could also be to easily flip off Copilot momentarily and code out the answer manually.

3. Refactor

TDD represented as a three-part wheel with the 'Refactor' portion highlighted on the bottom third

Refactoring in TDD means making incremental modifications that enhance the maintainability and extensibility of the codebase, all carried out whereas preserving habits (and a working codebase).

For this, we’ve discovered Copilot’s capability restricted. Contemplate two situations:

  1. “I do know the refactor transfer I wish to attempt”: IDE refactor shortcuts and options similar to multi-cursor choose get us the place we wish to go quicker than Copilot.
  2. “I don’t know which refactor transfer to take”: Copilot code completion can not information us by way of a refactor. Nevertheless, Copilot Chat could make code enchancment strategies proper within the IDE. We’ve began exploring that characteristic, and see the promise for making helpful strategies in a small, localized scope. However we’ve not had a lot success but for larger-scale refactoring strategies (i.e. past a single technique/operate).

Typically we all know the refactor transfer however we don’t know the syntax wanted to hold it out. For instance, making a take a look at mock that will enable us to inject a dependency. For these conditions, Copilot will help present an in-line reply when prompted by way of a code remark. This protects us from context-switching to documentation or internet search.


The frequent saying, “rubbish in, rubbish out” applies to each Information Engineering in addition to Generative AI and LLMs. Said in a different way: greater high quality inputs enable for the aptitude of LLMs to be higher leveraged. In our case, TDD maintains a excessive stage of code high quality. This prime quality enter results in higher Copilot efficiency than is in any other case doable.

We subsequently suggest utilizing Copilot with TDD, and we hope that you simply discover the above ideas useful for doing so.

Due to the “Ensembling with Copilot” staff began at Thoughtworks Canada; they’re the first supply of the findings lined on this memo: Om, Vivian, Nenad, Rishi, Zack, Eren, Janice, Yada, Geet, and Matthew.



Please enter your comment!
Please enter your name here