hard20 pts · first answer countstest-datatest-isolation

Leftover test data

Tests create data and delete it in afterEach. When a run is cancelled or crashes, junk data builds up in the shared environment and breaks list and search tests. What is the most robust design?

A.Tag created data with a run id and unique prefix, have tests ignore other runs' data, and run a scheduled sweeper that deletes old tagged dataB.Put cleanup in a try/finally inside every testC.Ask people not to cancel CI runsD.Drop and recreate the environment database each hour

Discussion 0

Join free to post in the discussion.

Leftover test data

Discussion 0

Related questions