Changes

Jump to: navigation, search

Testing Gramps

251 bytes added, 00:56, 29 March 2022
m
add-on > addon ( stick with one spelling )
=Test Automation=
Since 2016 2022 we have have test automation on [https://travisgithub.com/gramps-ci.orgproject/gramps/actions/githubworkflows/gramps-project Travisci.yml?query=branch%3Amaster GitHub Actions]. Status of all branches is [https://travis-cigithub.org/githubcom/gramps-project/gramps/branches actions/workflows/gramps-ci.yml here].
Travis GitHub Actions configuration is in [https://github.com/gramps-project/gramps/blob/master/.travisgithub/workflows/gramps-ci.yml .travisgramps-ci.yml].
What tests does Travis GitHub Actions run? This is determined by the script line in [https://github.com/gramps-project/gramps/blob/master/.travisgithub/workflows/gramps-ci.yml .travisgramps-ci.yml].nosetest3 runs all modules or folders named *[Tt]est. * [https://docs.github.com/en/actions GitHub Actions Documentation]
=Test status=
|}
{{man note|Note from Nick Hall|Some of the merge tests are slow because they actually run Gramps from the command line to import and export files.<br><br>Extra packages and add-ons addons are required to run some of the tests. From memory, you will need the
* Gramps addons
** CliMerge

Navigation menu