This section of the wiki will be used to document the various tests that must be run in order to validate Fedora 6.document details both the categories of tests that help in understanding Fedora's performance and scalability characteristics, as well as the tools used to perform those tests. This documentation is an aggregation of various testing initiatives from within the Fedora community over the last several years. Although the tooling has been updated to work with the most recent version of Fedora (6.0), it is important that the results produced through the current tests be compared to historical results in order to better understand the changes (improvements or degradations) in Fedora's performance characteristics over time.
Note: This testing approach was initially structured by the Product Technology Subgroup's: Fedora 6 Draft Test Plan
Test Categories
- API specification compliance
- OCFL compliance
- Ingest performance
- Read performance
- Versioning performance
- Search performance
- Migration performance and validation
Resources
...
Test Tooling
- Bash scripts used for measuring timing of fixed-scope operations.
- JMeter scripts used for measuring limits of scale and stress. These tests run until the application dies.
- Fedora API Test Suite is used to measure compliance of the Fedora application with the Fedora API specification.
- Python OCFL validator used to measure compliance of an OCFL structure with the OCFL specification