Difference between revisions of "Quality Assurance Initiative"
Jump to navigation
Jump to search
(Initial page version) |
|||
Line 22: | Line 22: | ||
* Code that nobody understands and maintains. | * Code that nobody understands and maintains. | ||
== Automated testing == | |||
[[File:Test pyramid.png|frame|right|The Test Pyramid illustrates the relative importance and the desired prevalence of tests at different coverage levels.]] |
Revision as of 20:25, 16 December 2023
![]() |
This page is a stub. You can help Inkscape Wiki by expanding it |
This page is a work in progress (2023-12-16).
The Quality Assurance Initiative aims to improve the quality and stability of Inkscape and to reduce the number of bugs and regressions, especially severe ones.
In a nutshell, the goal is to have more of:
- Test coverage of source code (unit tests, component/integration tests, end-to-end tests);
- Test automation, developer-friendly testing frameworks and tooling;
- Good practices related to coding and testing;
- Improvements to the code review process and release management;
- Focus on quality in all we do.
In this way, we would like to have less of:
- Crashes and data loss bugs;
- Memory leaks and corruption;
- Glitches, corner cases and difficult-to-reproduce bugs;
- Fragility due to hidden assumptions and limitations;
- Legacy code;
- Code that nobody understands and maintains.