Jump to: navigation, search

Testing Gramps

1 byte removed, 23:37, 7 July 2015
Possible improvements
* Unify running all the tests, in- or out- tree
** 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 [httphttps://sourceforgegithub.netcom/pgramps-project/gramps/source/ciblob/master/tree/gramps/test/ 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?){{bug|8294}}

Navigation menu