Use Verb Present Simple in QA like a PRO

In the world of Quality Assurance, we use the Present Simple to describe our testing cycles, expected system behavior, and the facts we document in bug reports.

Present Simple Formation

For I/you/we/they, use don’t in negatives and do in questions. For he/she/it, use doesn’t in negatives and does in questions.

When to use Present Simple in QA

1. Daily Routines and Agile Processes

Use this for actions that happen every day or every sprint. Signal words: every morning, during the stand-up, once a week.

• I check the backlog every morning.

• The team attends the stand-up at 10:00 AM.

• We perform regression testing once a week.

2. Technical Habits (Adverbs of Frequency)

Use these to describe how often you perform certain technical tasks. Adverbs: always, usually, often, sometimes, rarely, never.

• I usually use Postman for API validation.

• We never test in the production environment.

• The CI/CD pipeline automatically triggers a build.

*A CI/CD pipeline is an automated workflow that builds, tests, and deploys code. It bridges Continuous Integration (CI) (automated testing of code merges) and Continuous Delivery/Deployment (CD) (automated release to staging or production).

3. General Facts and Expected Behavior

This is critical for Expected Results in bug reports. Use this to describe how the software is designed to behave.

• The login button redirects the user to the dashboard.

• The system supports multi-factor authentication.

• This field validates the email format.

4. Timetables and Releases

• The release happens this Thursday.

• The maintenance window starts at midnight.

Ending S/ES with He/She/It 

In QA, “It” usually refers to the build, the app, the bug, or the tool.

1. Simple -s

Run → The automation suite runs overnight.
Report → The dashboard reports a 95% pass rate.

2. Verbs ending in -y

Verify / Retry / Modify (Consonant before ‘y’) → Change ‘y’ to ‘ies’.

• The script verifies the UI elements.
• The system retries the connection three times.

          Delay / Play (Vowel before ‘y’) → Just add -s.

• High latency delays the response time.

3. Verbs ending in s, sh, ch, x (Add -es)

• Fix → The developer fixes the critical issue.
• Crash → The app crashes on iOS 17.
• Pass → The test case passes successfully.

Professional Possessions: HAVE vs. HAS

In QA, we use “have” to discuss requirements, environments, and defects.

QA Tip: Always ask “Does the build have the latest fix?” (NOT: “Has the build…?”)

Asking Questions like a QA Engineer

Yes/No Questions (Sanity Checks)

• Do you see the same behavior in Staging?

• Does the database update after the transaction?

Wh- Questions (Root Cause Analysis)

• What does the error log show?

• How do we reproduce this crash?

• Why does the element disappear on hover?

• Who owns this microservice? (хто – subject)

• Who do you ask when you have questions? (кого – object)

QA Present Simple Vocabulary Set

Part 1: Fill in the Gaps 

Fill in the gaps with the correct form of the verb in brackets. Pay attention to (+), (-), and (?) symbols.

1. The automation script _______ (run) every night at 2:00 AM. (+)

2. We _______ (not / use) manual testing for this feature. (-)

3. How much time ______ it usually take for the developer _______ (fix) the bug in the build? (?)

4. It _______ (take) about five minutes to clear the cache. (+)

5. I _______ (not / see) the error logs in the console. (-)

6. _______ you _______ (have) access to the staging environment? (?)

7. She _______ (verify) the API response manually. (+)

8. The system _______ (not / support) this file format. (-)

9. _______ the QA lead _______ (assign) tasks every Monday? (?)

10. We _______ (perform) regression testing before every release. (+)

11. He _______ (not / write) code in Python; he prefers Java. (-)

12. _______ the page _______ (load) correctly on your side? (?)

13. The bug _______ (affect) only the mobile version of the app. (+)

14. They _______ (not / follow) the documentation strictly. (-)

15. _______ we _______ (need) to restart the server? (?)

16. The tool _______ (generate) a report after the test finishes. (+)

17. I _______ (not / reproduce) this defect on my machine. (-)

18. _______ she _______ (report) every minor issue she finds? (?)

19. The team _______ (conduct) a demo every Friday. (+)

20. It _______ (not / require) a high-speed connection. (-)

Part 2: Error Correction 

1. The app is crash every time I click the button.

2. Does he haves the latest version of the build?

3. We aren’t use Selenium for this project.

4. Why the script fails on the third step?

5. She always verify the requirements before testing.

6. I am not have the logs for this crash.

7. The system support multi-factor authentication.

8. Do the manager knows about the critical bug?

9. It don’t work on my environment.

10. How often do the team sync?

11. I haven’t access to the production server.

12. The script hasn’t any errors in the console.

13. Has the developer a fix for this ticket?

14. We haven’t enough time for full regression.

15. My laptop hasn’t the necessary drivers installed.

16. Have you the credentials for the database?

17. The new build hasn’t the bug we found yesterday.

18. Does the application has a dark mode option?

19. He haven’t a Jira account created yet.

20. They aren’t finish the testing on time.

Part 3: Speaking Section (QA Discussion)

1. What is your daily routine as a QA specialist?

2. How often do you run automation scripts?

3. What tools do you usually use for API testing?

4. How do you describe a bug to a developer who doesn’t agree with you?

5. Does your team have a daily stand-up meeting? What do you usually discuss?

6. How do you feel when a build fails right before a release?

7. What criteria do you use to decide if a bug is “critical” or “minor”?

8. Do you prefer manual testing or automation? Why?

9. How does the system behave when a user enters invalid data?

10. Who do you ask for help when the documentation is unclear?