STEP 63 OF 67 · YOU ARE THE QA TESTER

Retest the old after adding the new

Run the full playtest checklist after every merge, so no addition silently breaks something finished.

How to do it

  1. Play the first mission and the slice after each merge.
  2. Log anything broken and fix it before the next pass.
How AI speeds this up

Do it after every merged pass, before planning the next one.

Example from a sample game

Ashfall: a merged district broke a mission marker; caught the same day.

Before you move on

In Duke Forger, this step's gate checks:

Words to know

Regression
Something that worked before but broke after a change.
Do step 63 on your own game

Included in Creator, Academy and Studio. Duke drafts it with you and checks it before step 64 opens.

Start free