Changes

Jump to: navigation, search

Testing Gramps

1 byte added, 22:44, 28 September 2014
Possible improvements
** Try switching the feature tests and non-automated unit tests in test/ from our runner scripts to [http://docs.python.org/2/library/unittest.html#test-discovery python native unittest discovery mechanism].
** We have a stale [http://sourceforge.net/p/gramps/source/ci/master/tree/gramps/test/regrtest.py gramps/test/regrtest.py] runner, notable for logging init. - should we revive that, or maybe integrate into setup.py test runner?
* [https://wiki.python.org/moin/CodeCoverage|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