Alex beat me to it – the motor (if it is not 'stalled' somehow, will do as it is told. The software/driver will just produce pulses at regular intervals (unless interrupted) – it cannot suddenly decide to miss a pulse, or produce extra pulses. If it does, there is more likely to be a programming error!
Then if you need to check what the motor has actually done, you will need an encoder of some sort to send a return signal to the software. (and digital encoders of any accuracy tend to cost slightly more than the earth!)
As a general rule, stepper motor systems are 'open loop' systems – any commanded movement is assumed to have been completed successfully and is usually assured by using a motor with sufficient power to make the movement, and to hold its position after moving (i.e not slip forwards or back)
Servo systems, using an AC or DC motor with a feedback system as described by Roger Hart, are usually known as 'closed loop' systems, and many factors determine the eventual accuracy of movement.
What Martin seems to be describing is somewhat of a hybrid system, using a stepper motor with feedback in a closed loop configuration. Its possible, but maybe he can tell us what he will eventually apply this to – or is it just a learning exercise?