💻 LESSON 11 — Test Documentation

 💻 LESSON 11 — Test Documentation

🧠 Grammar: Much • Many • A lot of

🎯 Topic: Writing Test Documentation

🗣️ Skills: Speaking • Reading • Vocabulary • Grammar

Level: A2–B1 (QA Manual Testing)
Duration: 60 minutes

🎯 LESSON GOALS

By the end of this lesson, you will be able to:

✅ talk about test documentation

✅ describe the testing process

✅ explain what documents testers write

✅ correctly use much, many, a lot of

✅ discuss QA tasks confidently

>🔥 1. WARM-UP

🤔 "What kind of tester are you?"

Choose one answer and explain why.

1.

You discover 20 bugs before lunch.

What do you do first?

A) Celebrate 🎉

B) Write detailed bug reports 📝

C) Tell the developer immediately 💬

2.

Which is worse?

📄 Writing documentation

OR

🐞 Finding the same bug five times?

3.

Imagine your computer suddenly deletes all your documentation.

How would you feel?

4.

What is more important:

✔ finding bugs

or

✔ writing clear documentation?

Why?

5.

If you could remove ONE document from testing forever, which would you remove?

📚 2. VOCABULARY

Word	Meaning	Example
checklist	list of tasks	I always follow a checklist.
scenario	testing situation	This scenario checks the login page.
documentation	written project information	Good documentation saves time.
template	ready-made format	We use the same bug report template.
notes	short written information	I wrote some notes after testing.
procedure	step-by-step process	Follow the testing procedure carefully.
review	checking someone's work	My colleague reviewed the document.
approval	official permission	The test plan needs approval.
release notes	document describing a new version	I read the release notes yesterday.
summary	short overview	Please write a short summary.

🎮 Vocabulary Challenge

📖 3. READING

The Mystery of the Missing Checklist 😂

Monday morning started badly.

Emma opened her laptop and took a deep breath.

Today she had many test scenarios to complete and a lot of documentation to finish before lunch.

She looked for her checklist.

It wasn't there.

She checked her desktop.

Nothing.

She looked in the project folder.

Nothing.

She even checked the Recycle Bin.

Still nothing.

After twenty stressful minutes, she finally asked her teammate,

"Have you seen my checklist?"

He smiled.

"Yes."

Emma looked relieved.

"Where is it?"

He pointed at her second monitor.

She had printed the checklist and carefully taped it to the screen on Friday afternoon.

She had been looking for the digital file while the paper copy had been right in front of her the whole time.

The whole team laughed.

Her manager said,

"Don't worry."

"We have many testers..."

"...but only a few can lose a document that is literally in front of their face."

Emma laughed too.

She added one more item to her checklist:

✅ "Look at the screen before searching the computer."

🧠 4. GRAMMAR

Much • Many • A lot of

MANY

Countable nouns

✅ many bugs

✅ many scenarios

✅ many documents

Example:

We have many test cases.

MUCH

Uncountable nouns

✅ much time

✅ much information

✅ much documentation

Example:

We don't have much time today.

A LOT OF

Both countable and uncountable

✅ a lot of bugs

✅ a lot of information

✅ a lot of reports

Example:

The tester wrote a lot of notes.

Quick Table

Countable	Uncountable
many bugs	much information
many scenarios	much documentation
many templates	much time
many reviews	much work

🎯 Grammar Practice

Choose:

much/many / a lot of

1. 
   

We have ______ test scenarios today.

1. 
   

There isn't ______ time before the release.

1. 
   

The tester wrote ______ useful notes.

1. 
   

How ______ documentation do you usually write?

1. 
   

How ______ bugs did you find yesterday?

1. 
   

There are ______ templates in this folder.

✏️ Correct the Mistakes

1. 
   

There are much scenarios.

1. 
   

We don't have many information.

1. 
   

I wrote much notes.

1. 
   

There isn't many time.

1. 
   

We have a lot documentation.

🎭 5. ROLE PLAY

QA Team Meeting

Teacher = Team Lead

Student = QA Engineer

Discuss:

✔ How many scenarios have you tested?

✔ How much documentation is finished?

✔ Does the summary need approval?

✔ Have you read the release notes?

✔ What should we review before release?

🧩 6. MATCH THE DOCUMENT

Match the document to its purpose.

Document	Purpose
Checklist	___
Summary	___
Release notes	___
Procedure	___
Template	___

Purposes:

A. Gives a standard format

B. Explains the main points briefly

C. Lists tasks to complete

D. Describes how to perform a task

E. Explains what changed in the software

🗣️ 7. SPEAKING PRACTICE

Answer in full sentences.

1. 
   

Which document do you think is the most important in testing?

Why?

1. 
   

Do you enjoy writing documentation?

Why or why not?

1. 
   

What happens if documentation is poor?

1. 
   

Would you rather write documentation or find bugs?

Explain.

1. 
   

What makes a good checklist?

1. 
   

Should every bug report follow the same template?

1. 
   

Have you ever forgotten an important document?

What happened?

1. 
   

If AI wrote all documentation, what would testers do instead?

🎯 8. FINAL TASK

Explain the Testing Process

Imagine a new tester joins your team.

Explain:

• what documents they need
• what order they should follow
• what happens before release
• why documentation matters

Use:

✔ checklist

✔ scenario

✔ documentation

✔ procedure

✔ review

✔ summary

✔ release notes

✔ approval

✔ many / much / a lot of

🏆 BONUS GAME

"Which Document Am I?"

🟢 "I tell users what changed in the new version."

🟢 "You follow me step by step."

🟢 "Without me, you may forget important tasks."

🟢 "I am short but contain the main ideas."

🟢 "Managers usually give me before publishing."

✍️ HOMEWORK

Write 10–12 sentences:

"How I Would Test a Login Page"

Include:

• at least 7 vocabulary words
• 2 sentences with "many"
• 2 sentences with "much"
• 2 sentences with "a lot of"
• a logical testing procedure from preparation to final summary.