Jump to: navigation, search

Testing Gramps

44 bytes added, 22:43, 28 September 2014
Possible improvements
** Try switching the feature tests and non-automated unit tests in test/ from our runner scripts to [ python native unittest discovery mechanism].
** We have a stale [ gramps/test/] runner, notable for logging init. - should we revive that, or maybe integrate into test runner?
* [|Coverage analysis]
* Continuous test status report, coverage, automatic deployment into win/mac/linux VMs (needs server capacity to be hosted online)(I can dream, can't I?)
* Automated regression tests for our GUI. The following links look interesting:

Navigation menu