Apache OpenOffice is loaded with testing code, but the code is in a mess and out of maintain. Even the most is not stable enough to give useful results. The code is too complex and not easy to get started. Apache OpenOffice need a standard and unified framework to simplify writing testing code. The talk will introduce the plan to refactor the testing code and update the progress.
Automated testing obviously is important to ensure Apache OpenOffice quality. In fact, Apache OpenOffice is loaded with testing code, but the code is in a mess and out of maintain. Even the most is not stable enough to give useful results. A number of testing frameworks exists in Apache OpenOffice code base, e.g. qadevooo, VCL testtool and convwatch. Several programming languages are used for testing, e.g. Java, Basic and C++. The code is complex and hard to maintain. It's not easy to get started. Apache OpenOffice need a standard and unified framework to simplify writing testing code. The talk will introduce the plan to refactor the testing code and update the progress.
Outline:
- Current Status of Apache Office Automated Testing
- Target of Test Refactor
- Refactor Testing Code to JUnit 4 Style
- GUI Testing
- API Testing
- Entry to Start Testing
- Next Tasks in Future
- Integration with buildbot
- Repository to Store Testing Result.
- Attract More Contributors