Explaining a bug

English for IT Professionals · Lesson 2 of 5 · B1 Intermediate. Explain a bug so clearly that a developer can reproduce it the first time.

  • B1 Intermediate
  • IT and tech
  • You found a bug and need to explain it on a call or in a ticket.

By the end of the lesson

  • I can say what goes wrong: it crashes, it throws an error, it times out.
  • I can give the steps to reproduce a bug in order.
  • I can compare the expected behavior with the actual behavior.

Key phrases

The language that does the work

A good bug report answers four questions: what happens, when it happens, how to reproduce it, and what should happen instead. Use these phrases to answer each one.

What happens

  • The app crashes when I tap Save.
  • The function throws an error when the list is empty.
  • The request times out after 30 seconds.
  • The button doesn't do anything.
  • The page loads, but the data is missing.

When and where

  • It happens when I change the language.
  • It only happens on Android.
  • It started after the last release.
  • It happens every time.
  • It happens about one time in five.

Steps, expected and actual

  • Here are the steps to reproduce:
  • First, log in as an admin. Then go to Settings.
  • I expected to see the invoice, but instead I got a blank page.
  • The expected behavior is a success message.

Reproducing it

  • I can reproduce it every time.
  • I can't reproduce it on my machine.
  • Which browser and version are you using?
  • Can you send me the logs and a screenshot?

Complete the bug report

Tap a gap, then tap the words that fit. Press Check when every gap is full.

1The app when I rotate the phone. It just closes, and I'm back on the home screen.
2The function a NullPointerException when the list is empty.
3The request after 30 seconds because the database query is too slow.
4I tried it on three different laptops, but I can't it.
5It on Safari. Chrome and Firefox are fine.
6I expected to see the invoice, but I got a blank page.

Model dialogue

A bug in the checkout

The situation

Nadia is a QA engineer at a food delivery startup. She found a bug in the new version of the app, and she calls Lucas, the mobile developer.

Nadia
Hi Lucas, do you have five minutes? I found a bug in the checkout, and I think it's a blocker for the release.
Lucas
Sure. What's going on?
Nadia
The app crashes when a customer uses a promo code and then changes the delivery address.
Lucas
Okay. Can you give me the exact steps to reproduce it?
Nadia
Yes. First, add any item to the cart. Then enter the code WELCOME10. After that, go back and change the address. When you tap Pay, the app closes.
Lucas
And what did you expect to happen?
Nadia
I expected to see the payment screen with the new delivery fee. Instead, the app crashes. It happens every time.
Lucas
Does it happen on iOS and Android?
Nadia
It only happens on Android. I tested it on three different phones, and iOS is fine.
Lucas
Strange. I tried something similar this morning on the emulator, and I couldn't reproduce it. Can you send me the logs?
Nadia
Sure, I'll attach them to the ticket with a screen recording.
Lucas
Perfect. I'll look into it right now and let you know.

Check

What happened?

Read the dialogue, then choose the best answer.

01When does the app crash?

02What does Nadia say about the different phones?

03What will Nadia send Lucas?

Common mistakes

Find the mistake

These mistakes are very common when people describe bugs in English. Tap the part of each sentence that is wrong.

Sentence 1

Sentence 2

Sentence 3

Sentence 4

Sentence 5

Practice

Which is clearer?

Choose

Choose the best answer

Choose the clearest way to describe the bug.

01The best title for a bug ticket:

02Which sentence gives expected and actual behavior?

03The developer can't make the bug happen. A good thing to say:

04A good question to ask when someone reports a bug:

Your turn

Report a real bug

Think of a real bug from your work, or a bug in an app you use. Write a short report using the frame. Then explain it out loud, as if you are on a call with a developer.

  1. The bug is in ______.
  2. It happens when ______.
  3. Steps to reproduce: first, ______. Then ______. After that, ______.
  4. I expected ______, but instead ______.
  5. It only happens on ______.

After the lesson

Keep practicing

Next time you write a bug ticket at work, write it in English with these four parts: what, when, steps, and expected vs actual.

Can you do it now?

Check yourself

  • I can say what goes wrong: it crashes, it throws an error, it times out.
  • I can give the steps to reproduce a bug in order.
  • I can compare the expected behavior with the actual behavior.

Want feedback on your own answers?Practice this with Thomas in a one-on-one lesson. He'll listen, correct what matters, and help you sound like yourself in English.

Book a lesson with Thomas

Spot a mistake on this page? Tell me