Jump to: navigation, search

Testing Gramps

919 bytes added, 12:28, 17 May 2020
Test Automation: Corrected my misunderstanding :)
=Test Automation=
Since 2016 we have test automation on [ Travis]. Status of all branches is [ here].
Travis configuration is in [ .travis.yml].
What tests does Travis run? This is determined by the script line in [ .travis.yml].
nosetest3 runs all modules or folders named *[Tt]est.
=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. :-(
==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 [http 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}}
* Automated regression tests for our GUI. The following links look interesting:
** [ Python Wiki:GUI Testing Tools]
=Tests and frameworks used=
== Manual test plan ==
See [httphttps://sourceforgegithub.netcom/pgramps-project/gramps/source/ciblob/master/tree/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 ==
See more specialized scripts in [httphttps://sourceforgegithub.netcom/pgramps-project/gramps/source/citree/master/tree/test/ test/], status unknown.
Contents of [httphttps://sourceforgegithub.netcom/pgramps-project/gramps/source/citree/master/tree/test/ test/] :
* GrampsLogger/
==== test/ ====
'''[httphttps://sourceforgegithub.netcom/pgramps-project/gramps/source/ciblob/master/tree/test/ test/]''' - Report test for Gramps: Generate every report in every format. Runs all possible reports using the report cli interface, based on the [[example.gramps ]] database. This test is not fully self-contained, in that it depends on various environment settings, such as your locale, your preferred name display formats, and your report options. Last, but not the least, the verification of the resulting reports is entirely manual.
Bugs tagged as []
'''[httphttps://sourceforgegithub.netcom/pgramps-project/gramps/source/ciblob/master/tree/test/ test/]''' - Import/export test for Gramps.
From the file header:
== Unit testing ==
=== test/ ===
'''[httphttps://sourceforgegithub.netcom/pgramps-project/gramps/source/ciblob/master/tree/test/ test/]''' - Testing framework for performing a variety of unittests for Gramps. Runs out-of-tree (not in gramps/) testing code, by looking for any test/* files and executing the test suites therein. See the current code in test/* for example and python standard unittest docs.
{{man note|Starting with gramps4.x branch|these tests include non-automated unit tests only. The automated unit tests are all under gramps/.}}
{{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 are required to run some of the tests. From memory, you will need the
* Gramps addons
** CliMerge
** ExportRaw
*and the python packages.
** libxml2
** libxslt
** mocking
==== semi-interactive ====
! Comments
|[httphttps://sourceforgegithub.netcom/pgramps-project/gramps/source/citree/master/tree/gramps/gen/ gramps/gen/]
|bgcolor="#ff8080"| To Do
|Relationship calculator
* [[Unit Test Quickstart]]
* [[Test_date_handlers#TO_CHECK]]
* [[Gramps_Performance#The_Test_Results]]
* [[Test Imports module]]
[[Category:Developers/Quality Assurance]]

Navigation menu