Lesson 20 – Regression Testing


Lesson 20 – Regression Testing

Topic: Regression Testing & Software Releases

Grammar: Will vs. Be Going To

Lesson Objectives

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

  • discuss regression testing confidently;

  • describe the testing process before a release;

  • talk about future plans and predictions using will and be going to;

  • explain testing stages using professional QA vocabulary.

1. Warm-up

Answer the questions in complete sentences.

  1. What testing are you working on this week?

  2. Is your team going to have a release soon?

  3. What usually happens before a production release?

  4. Have you ever stopped a release because of critical defects?

  5. What do you think makes regression testing important?

2. Vocabulary

Key Vocabulary



Regression testing (регресійне тестування)

  1. We are going to perform regression testing after the new feature is implemented.

  2. Regression testing will help us find unexpected issues.

  3. Our team performs regression testing before every release.

  4. We are going to finish regression testing by the end of the day.

  5. The release won't start until regression testing is complete.

Smoke testing (димове тестування / перевірка збірки)

  1. We always begin with smoke testing.

  2. I'm going to run smoke testing as soon as the new build is ready.

  3. If smoke testing fails, we won't continue with other tests.

  4. The QA team will complete smoke testing in about 15 minutes.

  5. Smoke testing showed that the application was stable.

Sanity testing (санітарне тестування)

  1. I'm going to perform sanity testing after the bug fix.

  2. Sanity testing will confirm that the new feature works correctly.

  3. We don't need full regression testing—only sanity testing.

  4. The QA engineer completed sanity testing in twenty minutes.

  5. We will start sanity testing after deployment.

Stable (стабільний)

  1. The build looks stable now.

  2. We are going to test the stable version tomorrow.

  3. I think this release will be more stable than the previous one.

  4. The application became stable after the latest fixes.

  5. We won't deploy an unstable build to production.

Release (реліз, випуск)

  1. The next release is going to be on Friday.

  2. We will postpone the release if we find critical defects.

  3. The release includes several new features.

  4. Our team is preparing for the next release.

  5. I think the release will be successful.

Defect (дефект, помилка, баг)

  1. I found a critical defect in the payment module.

  2. The developer is going to fix the defect today.

  3. We will report every defect we discover.

  4. This defect affects several users.

  5. The QA engineer retested the defect after it was fixed.

Retest (повторно протестувати)

  1. I'm going to retest the login feature after the fix.

  2. We will retest all critical defects tomorrow.

  3. The QA engineer had to retest the issue several times.

  4. Please retest the bug before closing the ticket.

  5. I will retest the application after the new build is available.

Verification (верифікація)

  1. We are going to complete verification before the release.

  2. Verification ensures that the software meets the requirements.

  3. The team will begin verification this afternoon.

  4. Verification is an important part of the testing process.

  5. We can't deploy the application until verification is finished.

Validation (валідація)

  1. Validation confirms that the product meets users' needs.

  2. We are going to perform validation after regression testing.

  3. The client will participate in validation next week.

  4. Validation is almost complete.

  5. The release won't happen until validation is finished.

Production (продакшн, робоче середовище)

  1. The application is going to production tonight.

  2. We will monitor the system after the deployment to production.

  3. A critical bug was discovered in production.

  4. Never test experimental features in production.

  5. I think the deployment to production will go smoothly.

3. Reading

A Busy Day Before the Release

Tomorrow is release day. The QA team is going to test the new build.

First, they perform smoke testing. The build is stable, so they begin regression testing.

After an hour, Mia finds a critical defect in the login page. She tells the developers about the problem.

"We'll fix it right now," says one developer.

While the developers are working, the QA team continues testing other features.

Soon, the new build is ready. Mia is going to retest the defect. Everything works correctly this time.

"Great!" says the QA Lead. "The release will go to production tonight."

Everyone is happy and hopes the users will enjoy the new version.

4. Grammar

Practice 




5. Speaking Practice

Situation 1 – Release Planning

Answer the questions.

  • What testing are you going to do tomorrow?

  • What will happen after regression testing?

  • What do you think will be the biggest challenge?

Situation 2 – Team Meeting

Your manager asks:

  • What are you going to test first?

  • Which defects are you going to retest?

  • When is the release going to production?

  • Do you think users will find any issues?

Situation 3 – Prediction

Look at the situation.

  • There are 25 failed automated tests.

  • Two developers are still fixing bugs.

  • The release is tomorrow morning.

Discuss.

  • What is going to happen?

  • What will probably happen?

  • Should the team postpone the release?

6. Useful Sentences

Planning

  • We are going to perform regression testing tomorrow.

  • We are going to retest all resolved defects.

  • The team is going to deploy the release tonight.

  • We are going to verify the final build.

Predictions

  • I think the release will be successful.

  • We will probably find more bugs.

  • The build will be stable after the fixes.

  • Users will notice the improvement.

During Testing

  • I'll check the logs.

  • I'll verify the fix.

  • I'll update the test report.

  • We'll finish regression testing today.

8. Role Play

You are a QA Engineer preparing for tomorrow's release.

Explain:

  • what testing your team is going to perform;

  • what developers are going to do;

  • what you think will happen during regression testing;

  • whether the release will be successful.

Use at least six vocabulary words and five future forms (will and going to).

9. Error Correction

Correct the mistakes.

  1. We will going to perform regression testing tomorrow.

  2. I going to retest the defect.

  3. The release will goes to production tonight.

  4. We are going deploy the application tomorrow.

  5. I think we are going to find no bugs because the last build was unstable.

10. Homework

Writing (150–180 words)

Your team is preparing for a software release next week.

Write about:

  • what testing your team is going to perform;

  • what developers are going to do before the release;

  • what you think will happen during regression testing;

  • whether the release will be successful and why.

Use at least 8 vocabulary words from this lesson and include at least 5 examples of will and 5 examples of be going to.



Коментарі

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

Популярні дописи з цього блогу