Currently many autocorrection related tests have to be run as manual tests. We cannot create reliable automated tests because the result of spell checking is affected by the history of user's response to autocorrection. There is a new SPI in AppKit to disable user data, which enables us to obtain consistent spellchecking result. We should modify our testing harness to disable user spell checking data. There're two ways to do this: 1. Set user defaults before start running tests. This seems to be the easiest way. 2. Hook up the said SPI with javascript side, so that we can turn on/off user spell checking data on per test basis. Any suggestion on how we should go about this?
(In reply to comment #0) > Currently many autocorrection related tests have to be run as manual tests. We cannot create reliable automated tests because the result of spell checking is affected by the history of user's response to autocorrection. There is a new SPI in AppKit to disable user data, which enables us to obtain consistent spellchecking result. > > We should modify our testing harness to disable user spell checking data. There're two ways to do this: > > 1. Set user defaults before start running tests. This seems to be the easiest way. > 2. Hook up the said SPI with javascript side, so that we can turn on/off user spell checking data on per test basis. > > Any suggestion on how we should go about this? I can’t think of a reason we’d want to do (2).