The first actual bug: the past continuous for describing a bug

About this lesson

The past continuous and past simple for describing a bug are what this B1 English for IT lesson plan teaches.

Grammar
Was or were + -ing for the action in progress and the past simple for the event that interrupts it, joined by when or while: It froze while I was uploading.
Topic
Bug reports from merchants and support calls at a fictional payments startup, with words such as freeze, crash, timeout and workaround.
Activities
The 1947 moth story, a merchant's email, a support call and a voicemail, self-checking drills, a support chat and a wheel, then a message to write and a story to record.

What's inside

  1. Chapter 1Warm-up: Something Went Wrong

    • PictureUnlock
    • Open a box and answerOpen the boxUnlock
    • Study the words for bugs and crashesVocabularyTry it
    • Look at the pictures and choose the wordChoose by pictureUnlock
  2. Chapter 2The Story: A Moth in the Machine

    • Read the story: the first actual bugArticleUnlock
    • True or false? Check the storyTrue or falseUnlock
  3. Chapter 3At Work: The Frozen Upload

    • Read the email Fatima forwarded to WesReal-life documentTry it
    • Choose the answers a developer needsQuizUnlock
    • Sort the sentences into the parts of Erin's reportSort into columnsUnlock
  4. Chapter 4Listen: What Were You Doing?

    • Listen to Fatima's call with WesListeningTry it
    • Transcript, for the teacherUnlock
    • True or false? Check the callTrue or falseUnlock
    • Listen to Fatima's voicemail for ErinListeningUnlock
    • Transcript, for the teacherUnlock
    • Choose the correct answer about the voicemailQuizUnlock
  5. Chapter 5Grammar: It Froze While I Was Uploading

    • Study the scheme: past simple and past continuousGrammar schemeTry it
    • Fill in the table: past simple and past continuousFill in the tableTry it
    • Choose the past simple or the past continuousChoose the optionUnlock
    • Fill in the gaps: turn the log into sentencesFill in the gapsUnlock
    • Drag the verbs into the support messageDrag and dropUnlock
  6. Chapter 6Speak Up: Tell Me What Happened

    • Choose the best replies to a merchantChatTry it
    • Spin the wheel and tell your storySpin the wheelUnlock
  7. Chapter 7Homework: Your Bug Story

    • Read your phrase bankReal-life documentUnlock
    • Put the verbs in the past continuous: questions and answersFill in the gapsUnlock
    • Unscramble the bug wordsAnagramUnlock
    • Write a support message about a problem you hadWriting, checked by the teacherUnlock
    • Record the story of a bugSpeaking, checked by the teacherUnlock

Vocabulary

12 words and phrases from the lesson, each with a picture and audio in edio.

+9 more with pictures and audio in the lessonMore words

  • crash
  • freeze
  • upload
  • reproduce
  • an error message
  • a screenshot
  • a timeout
  • a workaround
  • intermittent

Grammar: past simple and past continuous for bug stories

A bug story has two layers: what was going on, and the moment something went wrong. Learners put the longer action in the past continuous and the short event that interrupts it in the past simple, join them with when and while, and keep state verbs such as know in the past simple.

Past simple and past continuous: the story of a bug

The longer action in the background: past continuous. The short event that interrupts it: past simple.

A longer action and a short event

The past continuous paints the scene: Erin was uploading a photo. The past simple gives the event that interrupts it: the app froze. A chain of short events takes the past simple too: The app froze, so I closed it and tried again.

A longer action and a short event

pastnow
  • Erin was uploading a photo
  • the app froze!

Which tense?

UseTenseExample
a longer action in progress (the background)past continuousI was uploading a photo…
a short event that interrupts itpast simple…when the app froze.
two longer actions at the same timepast continuous + past continuousWhile I was testing, Diego was updating the server.
short events, one after anotherpast simpleThe app froze, so I closed it and tried again.
state verbs: know, need, want, likepast simpleI knew the password.

Was or were + -ing

The past continuous is was or were + -ing: she was uploading, What were you doing? Many past simple forms in bug stories are irregular: froze, broke, threw, went. The app was crash is wrong: say The app crashed.

The past continuous: was / were + -ing

SubjectPositiveNegativeQuestion
I / he / she / itwas uploadingwasn't uploadingWas she uploading?
you / we / theywere testingweren't testingWhat were you doing?

Irregular past forms for bug stories

  • freeze → froze
  • break → broke
  • throw (an error) → threw
  • run (a test) → ran
  • go (blank, off) → went
  • know → knew

When or while?

When usually introduces the short event, in the past simple: I was uploading a photo when the app froze. While introduces the longer action, in the past continuous: The app froze while I was uploading a photo.

when + past simple: the short event

  • I was uploading a photo when the app froze.
  • When I clicked Save, the page went blank.

while + past continuous: the longer action

  • The app froze while I was uploading a photo.
  • While Erin was uploading, her assistant was issuing a refund.

From 1947 to today

The examples mix 1947 and today: The moth was causing a problem, so the team removed it. While Erin was uploading the photo, her assistant was issuing a refund. A past time can frame an action in progress: In 1947, engineers were already using the word bug.

  • The moth was causing a problem, so the team removed it.background, then the event
  • In 1947, engineers were already using the word “bug”.an action in progress at that time
  • Erin was uploading a photo when the app froze.longer action + short event
  • While Erin was uploading the photo, her assistant was issuing a refund.two actions at the same time
  • Wes was fixing a typo when he broke the login page.longer action + short event

Spelling -ing and state verbs

Most verbs just add -ing, but freeze drops its e (freezing), and run and stop double the last letter (running, stopping). State verbs stay in the past simple, among them know, need and want: I knew the password, not I was knowing.

Spelling -ing and state verbs

Most verbs just add -ing: upload → uploading. A final -e goes: freeze → freezing. Short verbs like run and stop double the last letter: running, stopping. Try → trying. State verbs (know, need, want, like) stay in the past simple: I knew, not I was knowing.

Typical mistakes

  • While I uploaded the file, the app was freezing.

    While I was uploading the file, the app froze.

    the longer action: past continuous; the short event: past simple

  • The app was crash.

    The app crashed.

    was + -ing, or the past simple

  • When I was clicking Save, the page was going blank.

    When I clicked Save, the page went blank.

    two short events: past simple

  • I was knowing the password.

    I knew the password.

    know is a state verb

More lessons on this grammar: Past continuous lessons and exercises · Past simple lessons and exercises

Try the past simple and past continuous exercises

Try them yourself: these are the same exercises your students do in edio.

What's in the lesson

  • 12 auto-checked exercises
  • 3 games
  • 2 teacher-checked tasks
  • 2 real-life documents
  • 1 article
  • 1 grammar scheme
  • 1 set of word cards
  • 2 audio clips
  • 1 picture
  • 2 transcripts

The main objectives of this lesson are to:

  • describe a bug so a developer can work on it: what you were doing, what went wrong and what you did next
  • set the scene with the past continuous and add the short event in the past simple: I was uploading a photo when the app froze.
  • join two actions with while and when: While I was uploading the photo, my assistant was issuing a refund.
  • ask what a user was doing: What were you doing when the app crashed? Was anyone else using the account?

Lesson 7 opens unit 3 of English for IT B1 · Inside the Team, Bugs and tickets, which builds clear bug reports a colleague can reproduce. It takes the past continuous and the when and while of A2.2 lessons 9 and 10 into support work, and lesson 8 then turns a bug story into steps to reproduce. A developer needs both layers of the story: what the user was doing, and what went wrong.

After twelve word cards with pictures and audio, from relay and logbook to timeout and intermittent, students read about the moth found in a relay of Harvard's Mark II in 1947 and why the logbook note was a joke. At work, they read a merchant's bug report, forwarded by support, and hear an AI-voiced call in which support and a developer work out what was happening; a voicemail then gives the merchant a workaround. The scheme leads into four drills that check themselves, among them a table with both past forms of eight verbs.

Speaking opens with a support chat in which students reply to a merchant, asking What were you doing when the app crashed?, then a wheel of bug stories and a support role-play. At home, students read a phrase bank and do a gap-fill of past continuous questions and an anagram of bug words, which check themselves, then write a support message and record the story of a bug for the teacher to review.

Grammar:
past continuous · past simple vs past continuous · when and while
Topic:
bugs · bug reports · computer history

Teaching tips

  • Turn a log into a story: write timed entries on the board, such as 2:40–2:45 upload photo and 2:41 app freezes, and let learners join them with when or while.
  • Play the support agent: one learner reports a frozen app in one vague line, and the other may ask only past continuous questions, such as What were you doing? and Was anyone else using it?, until the story is clear.
  • One-to-one, start from the learner's last bug: they tell it with I was… when… while you write it down, then you underline every verb together and check which ones needed -ing.
  • Let non-developers tell their own bugs: in an in-company group, testers, designers and support staff describe a problem with a printer, a video call or a banking app, as the writing task allows.

Liked it?

Teach the whole lesson in edio

27 exercises in 7 chapters, ready to teach. edio is an online platform for language schools and teachers: ready-made interactive lessons, live classes, homework and student progress in one place.

  1. Start a free trial

    7 days, no credit card.

  2. Open the lesson

    Find it in the library of 621 ready lessons. Teach it as it is, or copy any chapter into your own lessons.

  3. Teach it live or as homework

    Students work in their own accounts, in sync with you during the lesson, and the practice exercises check themselves.

The whole course: English for IT B1 · Inside the Team

24 lessons at B1 for people who build, test or run software, in American English. Learners follow Iryna, a junior developer, through her first year at Kestrel Cloud, a fictional payments startup: standups, tickets, code review, chats across time zones and job interviews. Each lesson is built around a true story from software history.See the course

  1. Unit 1 Hello, team

    roles, stacks and first days: the present simple, the present perfect with for and since, question forms

    1. Lesson 1How big is a two-pizza team?Present simple for jobs and responsibilities
    2. Lesson 2Your first "Hello, World"Present perfect with for and since
    3. Lesson 3Write your personal READMEQuestion forms for getting to know colleagues
  2. Unit 2 The daily standup

    updates and blockers: the present simple and continuous, just, already and yet, have to and need to

    1. Lesson 4Why is it called a scrum?Present simple vs continuous and state verbs
    2. Lesson 5Done, not done yetPast simple, present perfect and going to for updates
    3. Lesson 6Help, I'm blocked!Have to, need to, don't have to and can't
  3. Unit 3 Bugs and tickets

    clear bug reports: the past continuous, imperatives and the zero conditional, quantifiers

    1. Lesson 7 · you're hereThe first actual bugPast simple and past continuous for bug stories
    2. Lesson 8Steps to reproduceImperatives and the zero conditional for bug reports
    3. Lesson 9The email that couldn't go 500 milesQuantifiers in bug tickets
  4. Unit 4 Code review

    kind, useful comments: -ed and -ing adjectives, modals for suggestions, the first conditional

    1. Lesson 10What's a nit?-ed and -ing adjectives in review comments
    2. Lesson 11Could we maybe…?Modals for suggestions in code review
    3. Lesson 12Your first pull requestThe first conditional and unless in code review
  5. Unit 5 How it works

    explaining systems step by step: time clauses, the passive, relative clauses

    1. Lesson 13What happens when you type a URL?Time clauses with as soon as, until and once
    2. Lesson 14How is a barcode read?The present and past simple passive
    3. Lesson 15Draw it, then say itDefining relative clauses
  6. Unit 6 Remote and async

    chat, email and time zones: polite requests, future forms, the present perfect continuous

    1. Lesson 16Just say what you needPolite requests and indirect questions
    2. Lesson 17Your 9 a.m. is my noonFuture forms for plans across time zones
    3. Lesson 18Write it downPresent perfect continuous for status updates
  7. Unit 7 Users and clients

    user stories and plain explanations: verb + to or -ing, reported speech, comparisons

    1. Lesson 19As a user, I want…Verb + to or verb + -ing
    2. Lesson 20"The client said it was broken"Reported speech for client calls
    3. Lesson 21Explain it in ten hundred wordsComparisons for plain explanations
  8. Unit 8 Your next job

    resumes and interviews: used to, the past perfect, the second conditional

    1. Lesson 22A resume that shows resultsUsed to for your career path
    2. Lesson 23Tell me about a time when…The past perfect for STAR stories
    3. Lesson 24What would you do if…?The second conditional for interviews

Questions about this lesson

How do you use the past simple and past continuous to describe a problem?
Use the past continuous for what was going on and the past simple for what went wrong: I was uploading a photo when the app froze. What you did next stays in the past simple: I closed the app. Add other background actions too: At the same time, my assistant was issuing a refund. The B1 English for IT lesson The first actual bug on edio.ai builds a merchant's report this way.
How do you use while in English grammar?
While introduces the longer action, usually in the past continuous: The app froze while I was uploading a photo. It also joins two actions in progress at the same time: While Jordan was testing the login screen, Diego was updating the server. Put a comma after the while clause when it comes first. For the short event, use when with the past simple: When I clicked Save, the page went blank.
How do you show an action was interrupted in the past?
Put the interrupted action in the past continuous and the interruption in the past simple: I was fixing a typo when I broke the login page. Diego was sleeping when an alert went off. The longer action was still going on when the short event happened. A drill in The first actual bug, a B1 English for IT lesson on edio.ai, turns timed log entries into such sentences.
Is it "while I uploaded" or "while I was uploading"?
It's while I was uploading, in the past continuous, because while introduces the longer action: While I was uploading the file, the app froze. The short event takes the past simple, so the app was freezing is wrong here too. The scheme of The first actual bug on edio.ai lists this pair among its typical mistakes.
Is it "the app was crash" or "the app crashed"?
It's the app crashed, in the past simple: was never goes with a bare verb. For an action in progress, was needs the -ing form: The app wasn't responding, so I closed it. A support chat in The first actual bug, from the English for IT B1 course on edio.ai, offers when the app was crash as a wrong reply.
Why is a software error called a bug?
Engineers called small hidden faults bugs long before computers. Thomas Edison wrote about bugs in his inventions in the late 1870s. In 1947, the team running Harvard's Mark II found a real moth in a relay and taped it into the logbook as the first actual case of a bug being found: a joke, because the word was already in use. Today, to debug means to find and remove mistakes in code.
How do you describe a bug in English?
Describe a bug in three parts: the background, the problem, your next step. I was joining a video call when the app suddenly froze. While I was trying to close the window, an error message appeared. I restarted the laptop and joined again. Then add what a developer needs: the exact error message, your device and app version, a screenshot and any workaround.
What's the difference between a crash and a freeze?
An app that crashes stops suddenly and closes by itself; an app that freezes stops responding, but the screen stays the same. The app crashed and closed. The app froze at about 80%, and the buttons didn't respond. In the past simple, crash is regular (crashed), but freeze is irregular (froze). Quote any error message word for word, such as Upload failed: request timeout (408).
What is a workaround?
A workaround is a temporary way to get the job done despite a problem, while the real fix is still coming. Support teams offer one so users can keep working: Here's a workaround: you can check your payouts in the web dashboard on a laptop. In a bug report, say what you tried and what worked: Workaround: I tried again when nobody was using the laptop, and the upload worked.
How do I teach the past simple and past continuous with work stories?
Draw a timeline before any rule: a long line for the action in progress, a cross for the event that interrupts it. Then collect real stories, such as a time an app froze, and build each one on the board: I was presenting my screen when the call dropped. Finish with questions in the past continuous: What were you doing? Was anyone else using it?
Are there interactive exercises for the past continuous in bug reports?
Yes: self-checking tables and support chats train both tenses. No account is needed for the four parts of The first actual bug, a B1 English for IT lesson on edio.ai, that play on this page: a merchant's email about a frozen upload, a call between support and a developer, a table of past simple and past continuous forms, and a chat in which students reply to a merchant whose app crashed. Everything else stays locked.

Teach this lesson with your students

No credit card required