Lesson 5 - reporting bugs
🐞 LESSON 5 — Reporting Bugs
💻 A2–B1 Individual Online English Lesson (60 minutes)
🎯 Topic: How to Report a Bug Clearly
🧠 Grammar: Imperatives + Sequencing Words
🗣️ Speaking: Explain how to reproduce a bug
🎯 Lesson Goals
By the end of this lesson, you can:
✅ describe a software bug clearly
✅ explain steps to reproduce a bug
✅ use sequencing words correctly
✅ write a simple bug report
✅ speak like a QA tester 🧑💻
🔥
1. WARM-UP (5–7 min)
💬 Discussion Questions
💻 Do you use mobile apps every day?
🐞 Have you ever found a bug in an app?
😤 What is the most annoying software problem?
📱 What happens when an app crashes?
🧑💻 Why is software testing important?
Sample Answers
💬 Yes, I use apps every day.
💬 Sometimes I find bugs in websites.
💬 A login problem is very annoying.
🖼️ Let's Look at Software Testing
📚 2. VOCABULARY
🐞 Reporting Bugs Vocabulary
| Word | 🇺🇦 Ukrainian | Example Sentence | |
|---|---|---|---|
| 🔄 reproduce | відтворити | I can reproduce the bug every time. | |
| 📝 steps | кроки | Follow these steps carefully. | |
| ✅ expected result | очікуваний результат | The expected result is a successful login. | |
| ❌ actual result | фактичний результат | The actual result is an error message. | |
| 📸 screenshot | скріншот | Please take a screenshot. | |
| 🚨 severity | серйозність | This bug has high severity. | |
| 🔥 priority | пріоритет | The priority is high. | |
| 🌐 environment | середовище | The bug appears in Chrome. | |
| 📄 description | опис | Write a clear description. | |
| 📎 attach | прикріпити | Please attach the screenshot. |
🎯 Vocabulary Practice
Match:
Picture of the screen → ________
What should happen → ________
Add a file → ________
Actions to follow → ________
Make the bug happen again → ________
📖 3. READING
🐞 The Strange Login Bug
Tom works as a QA tester. 💻
One morning, he found a bug in a mobile application. 📱
First, he opened the application.
Then he clicked the login button.
After that, he entered his username and password.
Finally, he clicked "Log In".
The expected result was to open the homepage. ✅
However, the actual result was an error message. ❌
Tom could reproduce the bug every time.
He wrote a clear description and included all the steps.
Then he took a screenshot and attached it to the bug report. 📸📎
The bug had high severity and high priority because users could not log in.
❓ Reading Comprehension
What is Tom's job?
What bug did he find?
What was the expected result?
What was the actual result?
What did Tom attach?
🧠 4. GRAMMAR
Imperatives
👉 We use imperatives to give instructions.
Structure
Verb + object
Examples
✅ Open the application.
✅ Click the login button.
✅ Enter your password.
✅ Attach a screenshot.
✅ Save the report.
Negative Imperatives
❌ Don't close the browser.
❌ Don't skip any steps.
Sequencing Words
These words help us explain a process.
| Word | Meaning |
|---|---|
| 1️⃣ First | спочатку |
| 2️⃣ Then | потім |
| 3️⃣ After that | після цього |
| 4️⃣ Finally | нарешті |
Examples
📱 First, open the application.
👆 Then, click the login button.
⌨️ After that, enter your password.
✅ Finally, click Submit.
🗣️ 5. SPEAKING PRACTICE
How to Reproduce a Bug
💬 First, open the application.
💬 Then, click the login button.
💬 After that, enter incorrect data.
💬 Finally, click Submit.
💬 The application crashes.
🖼️ Picture Discussion
Questions
📱 What problem can you see?
📸 Why is a screenshot useful?
🧑💻 What should the tester do next?
🚀 FINAL SPEAKING TASK
🎤 Explain a Bug Report
Imagine you found a bug.
Describe:
✅ environment
✅ steps
✅ expected result
✅ actual result
✅ severity
✅ screenshot
Useful Model
💬 I found a bug in a mobile application.
💬 First, I opened the app.
💬 Then, I clicked Login.
💬 After that, I entered my password.
💬 Finally, I clicked Submit.
💬 The expected result was a successful login.
💬 The actual result was an error message.
💬 I attached a screenshot.
✍️ WRITING TASK (Homework)
Write a short bug report (8–10 sentences).
Use:
🔄 reproduce
📝 steps
📄 description
📸 screenshot
🚨 severity
🔥 priority
Example Start
🐞 Bug: Login Error
First, open the application.
Then click the login button.
After that, enter your username and password.
Finally, click Log In.
The expected result is successful login.
The actual result is an error message.
🎉 Great Job!
You can now:
✅ report bugs professionally
✅ explain steps clearly
✅ use sequencing words confidently
✅ communicate like a QA tester 🐞💻🚀


Коментарі
Дописати коментар