Difference between revisions of "Testing Inkscape"
Jump to navigation
Jump to search
m (link fix) |
(major cleanup, remove everything not up to date) Tags: Replaced Visual edit |
||
| (22 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
See https://inkscape.org/contribute/testing/ | |||
=== PROBABLY OUTDATED OLD STUFF - please clean up === | |||
A community of Inkscape testers has grown up which has its own [http://lists.sourceforge.net/lists/listinfo/inkscape-tester mailing list], and it is to be hoped that this will spearhead all work on usability and human factors. This group should be your first port of call for these areas: | |||
* [[ComplianceTesting]] | * [[ComplianceTesting]] | ||
==== Analyzing test coverage ==== | |||
To see how well the (unit) tests cover certain parts of the code, or to compare the coverage of rendering tests vs. unit tests, gcov can be used. See [[Profiling]] for more information on how to use gcov and coverage.py (a tool to get some grip on the massive amounts of data gcov can generate). | |||
[[Category:Help Wanted]] | |||
Latest revision as of 14:40, 26 May 2025
See https://inkscape.org/contribute/testing/
PROBABLY OUTDATED OLD STUFF - please clean up
A community of Inkscape testers has grown up which has its own mailing list, and it is to be hoped that this will spearhead all work on usability and human factors. This group should be your first port of call for these areas:
Analyzing test coverage
To see how well the (unit) tests cover certain parts of the code, or to compare the coverage of rendering tests vs. unit tests, gcov can be used. See Profiling for more information on how to use gcov and coverage.py (a tool to get some grip on the massive amounts of data gcov can generate).