The way this works currently is that we run the current stage and all previous stages in descending order - if the current stage fails, we don’t get to running the previous tests. If the current stage passes, we run the previous ones until one of them fails (or all of them pass).
I totally understand the use-case though, we’re going to add codecrafters test --previous early next week 
Related: Ability to run tests for previous stages