UI testing for v2.5?
Testing for OpenLP (rightly) focuses on verification and validation of the program's functionality. This ensures it is built right; testing for bugs, and checking it all works as expected.
How much has testing been utilised in the design phases? User testing can be particularly helpful in making UI decisions. It is one thing for devs to identify features that the program needs, but it is another to assume that since a particular UI setup works for them, and they've never had any issues with it, then that UI will work fine for all users.
See this topic for example discussion of a UI decision: http://openlp.org/en/forums/development/feature_requests/clear_distinction_between_verses_in_preview_and_live_view.html
Don't get me wrong, I think OpenLP has a great UI, and I don't want to change anything for v2.0! I'm just wondering how much scope there is to incorporate user testing in the future design process.
Useful testing could include: testing of different levels of users on the existing interface, on possible UI mockups, and on alternative programs (eg OpenSong, EasyWorship) - and analysing the positives and negatives of each interface for different users.