Reported by jteh on 2010-06-16 00:38
All testing of NVDA is currently done manually by its developers and users. This can be extremely time consuming and tedious. Also, there is a high potential for code changes to cause regressions in other (sometimes unforeseeable) circumstances and functionality. To alleviate these problems and to allow for faster discovery of new problems, an automated testing system needs to be developed for NVDA. This system would automatically run tests defined by the developers on a regular basis and report on the success or failure of the tests.
Due to the interdependence of much of the code and the inherent interaction between NVDA and other applications, unit testing the code is extremely difficult and much less useful than system testing. Therefore, at least initially, the focus will be system testing. System tests will examine NVDA's interaction with the operating system and other applications.
Reported by jteh on 2010-06-16 00:38
All testing of NVDA is currently done manually by its developers and users. This can be extremely time consuming and tedious. Also, there is a high potential for code changes to cause regressions in other (sometimes unforeseeable) circumstances and functionality. To alleviate these problems and to allow for faster discovery of new problems, an automated testing system needs to be developed for NVDA. This system would automatically run tests defined by the developers on a regular basis and report on the success or failure of the tests.
Due to the interdependence of much of the code and the inherent interaction between NVDA and other applications, unit testing the code is extremely difficult and much less useful than system testing. Therefore, at least initially, the focus will be system testing. System tests will examine NVDA's interaction with the operating system and other applications.