Grammarchecker testing and development
We have 3 approaches
- Grammarchecker development (building the program)
- Working with precision (are the alarms correct)?
- Testing precision and
recall (do we find all the errors)?
Grammarchecker development
- Find errors of the relevant type (= errors that we write rules for)
- Put the sentences containing these errors in yaml files in grammarchecker/tests
- Run the yaml test and revise the grammachecker.cg3 rules until all yaml sentences pass
Testing precision (are the alarms correct)?
- Find a large corpus (preferably written by the gramchecker’s target group and run it through the grammarchecker
- Look for alarms.
- If the goal is to test precision, calculate how many of the alarms are correct
- If the goal is to improve the gramchecker, put the sentences containing false (and why not correct ones!) in the yaml files and revise the grammachecker.cg3 rules until all yaml sentences pass
Testing precision and recall (do we find all the errors)?
Warning!!
Whole texts annotated for testing can not be used for improving the program. If so, you cannot use them for testing.