---
id: 67f3c585f2807bfec1fa2e03
title: Task 144
challengeType: 19
dashedName: task-144
lang: en-US
---

<!-- READING -->

# --instructions--

Read the text and answer the question below.

# --questions--

## --text--

After their conversation, Jessica followed up with an email to confirm the project details and share the updated timeline:

`Hi David,`

`As promised, here's the updated project timeline for the finance app, including more detail on where things stand:`

`April 8–9: Final bug fixes focused on minor user interface glitches discovered after main testing.`

`April 10: Quick round of regression testing to confirm all issues are resolved and nothing new has appeared.`

`April 11: Release preparation — packaging the build, updating documentation, and internal review.`

`April 12: App launch as planned.`

`We're still on schedule, and no major blockers have come up. Just to clarify, all core features are stable and performing well. The budget tracking feature is confirmed for the next release, which we're planning for later this month. I'll follow up soon with that timeline once it's finalized.`

`Let me know if there's anything else you'd like to go over.`

`Thanks,`

`Jessica`

What is scheduled to happen on April 10?

## --answers--

Bug fixing for UI glitches.

### --feedback--

Bug fixing is scheduled for April 8–9, not April 10.

---

Regression testing to confirm stability.

---

App launch and final review.

### --feedback--

The app launch is scheduled for April 12, not April 10.

---

Adding the budget tracking feature.

### --feedback--

The budget tracking feature is planned for a future update, not this one.

## --video-solution--

2

# --explanation--

To find the correct answer, pay attention to the section of the email where Jessica mentions what is happening on April 10.

It specifically describes the regression testing process to confirm that all issues have been resolved and that the system remains stable.

Look for the option that reflects this testing activity.
