Lesson 26 - Vocabulary & Grammar Revision + Test

 Lesson Overview

Vocabulary areas

  • Agile/project: sprint, backlog, story, epic, assign, status, progress, estimate, board, workflow
  • Web/UI testing: website, button, form, field, dropdown menu, navigation, broken link, responsive design, home page, user interface, device, Android, iPhone, screen size, orientation
  • Mobile actions: swipe, tap, install, crash, performance
  • API testing: API, request, endpoint, status code, JSON, authorization, header, payload, token
  • QA documentation: checklist, scenario, documentation, template, notes, procedure, review, approval, release notes, summary
  • Meetings: agenda, discussion, conference call, microphone, camera, mute, connection, presentation, participant, record

Grammar areas

  1. Prepositions of time: at / on / in
  2. Modal verbs: must / can't / may / might / could
  3. Past Simple — regular verbs
  4. Past Simple — irregular verbs
  5. much / many / a lot of
  6. should / shouldn't

2. Warm-up — QA Conversation

  1. What do you usually do during a sprint?
  2. What is the difference between a story and an epic?
  3. How do you know the status of a bug?
  4. What do you usually test on a website?
  5. What mobile devices do you test?
  6. Have you ever found a broken link?
  7. Have you ever tested an API?
  8. What do you usually discuss during a conference call?

3. Vocabulary Revision — Match the Words


4. Vocabulary Revision — Complete the Sentences



5. QA Documentation Vocabulary

Explain or elicit the meaning of:

  • checklist — a list of things to check
  • scenario — ?
  • documentation — 
  • template — 
  • notes — 
  • procedure — 
  • review — 
  • approval — 
  • release notes
  • summary — 

6. Meeting Vocabulary


7. Grammar Revision — Prepositions of Time

AT / ON / IN

  1. The sprint starts ___ Monday.
  2. We have a conference call ___ 10:30.
  3. The release is planned ___ September.
  4. I usually test APIs ___ the morning.
  5. The meeting is ___ Friday afternoon.
  6. We finished the project ___ 2026.
  7. The developer called me ___ noon.
  8. We need to finish this story ___ two days.
  9. I found the bug ___ Tuesday.
  10. We usually have a daily meeting ___ 9:15.

8. Grammar Revision  — MUST / CAN'T / MAY / MIGHT / COULD

  1. You ________ complete the security checklist before release.
  2. The server ________ be unavailable; I can't connect to it.
  3. Users ________ see different layouts on different screen sizes.
  4. You ________ share your authorization token with other users.
  5. The problem ________ be caused by the API. We need more tests.
  6. We ________ test the application on Android before release.
  7. The button ________ be disabled because the form is incomplete.
  8. A user ________ access this page without authorization.

  1. 9. Grammar Revision  — MUCH / MANY / A LOT OF

    1. We found ________ bugs.
    2. We don't have ________ time.
    3. The documentation contains ________ information.
    4. How ________ participants joined the call?
    5. How ________ progress have we made?
    6. There are ________ test scenarios.
    7. We don't have ________ information about the problem.
    8. The developer fixed ________ issues.
    9. How ________ tests did you run?
    10. We made ________ progress today.

10. Grammar Revision  — SHOULD / SHOULDN'T

Give advice for each situation.

  1. The application crashes when the user taps the login button.
  2. The website doesn't work correctly on small screens.
  3. The API returns 401.
  4. A test case has no expected result.
  5. The developer hasn't received the bug report.
  6. The release notes contain incorrect information.
  7. The connection is unstable during a conference call.
  8. A tester wants to release a feature without reviewing it.