Yes Ingo, that's a nice idea. I am using something like that for R-o-F testing:
e.g., the engine should find the following moves:
lg 1242741 : move 12 is A5 ;
lg 1170111 : move 30 is C2 ;
lg 1165916 : move 34 is M6 ;
lg 1241219 : move 14 is J3 ;
lg 1241197 : move 7 is B3 ;
lg 1240767 : move 19 is B4 ;
lg 1239553 : move 9 is G2 ;
lg 1239472 : move 13 is G2 ;
lg 1242768 : move 39 is E4 ;
lg 1242134 : move 9 is F5 ;
but in fact currently R-o-F gets at most two moves right from that list.
Thomas warns me that what might seem obvious to a human,
may not be the only move, or may even be totally wrong.
So one should perhaps not just test whether the engine
finds the move from the test spec, but also (in case it suggests another)
how the evaluation for the intended move actually was.