Question

A backend developer is adding Copilot-generated unit tests for a service class whose methods all depend on an in-memory cache that must be initialized before each test and cleared afterward. Copilot's first draft duplicates the cache setup and teardown code inside every individual test method. What is the most effective way to prompt Copilot to improve the generated test suite while keeping the tests correct?

Accepted Answer

Ask Copilot to refactor the duplicated setup and teardown into shared fixture lifecycle hooks (e.g., setUp/tearDown or beforeEach/afterEach) so each test starts from a clean, initialized cache.

Answer

Ask Copilot to delete the teardown code entirely since the in-memory cache will be garbage-collected between test runs anyway.

Answer

Ask Copilot to combine all the individual tests into a single large test method so the cache is only initialized once.

Answer

Ask Copilot to mark every test with a shared static cache instance and remove the per-test initialization to speed up execution.