Test and practice aren't two things you do. They're two halves of one machine.
Most people treat them separately: they practise for a while, or they take tests for a while, and progress comes slowly if at all. The people who improve fast do something different — they run test and practice as a single connected loop, where each one feeds the other. The test tells you what to fix; practice fixes it; the next test proves it moved. Separately, they're weak. Wired together, they compound.
Two words, one system
The reason "typing test and practice" belong in the same phrase is that neither does its real job alone. A test without practice is just a measurement you do nothing with. Practice without a test is just effort you can't aim. Put them together and each supplies exactly what the other lacks: direction and proof on one side, improvement on the other.
The feedback engine
Here's the system as a single loop. Watch the signal travel: the test produces data about your weak spot, that data aims your practice, practice produces improvement, and the next test confirms it — then the cycle runs again, a little higher each time.
This is what a feedback loop does that a straight line can't: it self-corrects. Every pass through the engine, your practice gets re-aimed at whatever the latest test exposed, so you're never drilling yesterday's problem. The loop keeps pointing your effort at the thing that's actually holding you back right now.
Why either one alone stalls
The clearest way to see the value of the system is to watch what happens when you break it — running only one half.
Test-only is the person who checks their speed weekly and wonders why it never changes — measuring a thing doesn't improve it. Practice-only is the person who grinds for hours but drifts, because without a test they can't tell a weakness from a strength, or whether anything is working. Only the loop turns motion into progress.
A weekly rhythm you can actually keep
The system doesn't need to be elaborate. A light weekly rhythm — bookend your week with tests, fill the middle with aimed practice — keeps the engine turning without taking over your life.
Monday's test sets the target; the midweek sessions drill it; Friday's test tells you whether it worked and sets next week's focus. That's the whole engine, running on about twenty minutes a day. Keep it turning for a season and the compounding does the rest. For the deeper science of the practice half, the practice-that-works guide goes further; for the measuring half, see how to check your typing speed.
Where to run the loop
TypeLords is built so the two halves live side by side. TypeTest is the measuring engine — graded, full-duration, with a certificate to mark progress — and TypePracticeis the fixing engine — an open arena with instant feedback. Run one into the other and you've got the whole system in one place.
So stop choosing between testing and practising. The phrase puts them together for a reason: they're one machine. Test to find the gap, practise to close it, test again to prove it — and let the loop carry your speed somewhere neither half could reach alone.