4,609
edits
Changes
m
=Test Automation=
Since 2022 we have test automation on [https://github.com/gramps-project/gramps/actions/workflows/gramps-ci.yml?query=branch%3Amaster GitHub Actions]. Status of all branches is [https://github.com/gramps-project/gramps/actions/workflows/gramps-ci.yml here].
GitHub Actions configuration is in [https://github.com/gramps-project/gramps/blob/master/.github/workflows/gramps-ci.yml .gramps-ci.yml].
What tests does GitHub Actions run? This is determined by the script line in [https://github.com/gramps-project/gramps/blob/master/.github/workflows/gramps-ci.yml .gramps-ci.yml].
nosetest3 runs all modules or folders named *[Tt]est.
* [https://docs.github.com/en/actions GitHub Actions Documentation]
=Test status=
As of Jan 2015 we don't have a record of tests executed, the platforms and environments they were run upon, and what code they covered. The only indirect evidence is available in open bugs, when people care to fill in these details. :-(
=Tests and frameworks used=
== Manual test plan ==
See [https://github.com/gramps-project/gramps/blob/master/TestPlan.txt TestPlan.txt] in gramps toplevel. (I believe this is only done at a major release (like Gramps version 4.0.0)).
== Specialized scripts for testing ==
|}
{{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 and ** ExportRaw add-ons, *and the python packages.** libxml2, ** libxslt and ** mocking python packages. Some of these may not be available for python3 yet.}}
==== semi-interactive ====