Currently Cobol Check, checks the validity of the unit test (.cut) syntax, by checking, if the last token, can be followed by the current token. This may catch a lot of syntax errors, however a lot can go unnoticed, and lead to unexpected behavior. Thus we need to make the syntax check context sensitive. When we enter an EXPECT-statement, Cobol Check needs to know that it is built the right way. The same goes for MOCK and VERIFY.
Currently Cobol Check, checks the validity of the unit test (.cut) syntax, by checking, if the last token, can be followed by the current token. This may catch a lot of syntax errors, however a lot can go unnoticed, and lead to unexpected behavior. Thus we need to make the syntax check context sensitive. When we enter an EXPECT-statement, Cobol Check needs to know that it is built the right way. The same goes for MOCK and VERIFY.