No. The test performed at the end of each backup is actually calling the exact same code as the TEST command, but limited in scope to avoid large overheads.
The test command is just intended for running verifications outside of the normal backup flow.