This page documents the minimum set of criteria and tests that must pass before a FOSSology release can be made.
As additional issues are discovered and our testing becomes more mature, expect this list to grow, and expect that more of these tests will become automated.
All new code (committed as part of 1.2 release and beyond) must have unit tests written for it.
We will test on the following Linux distros: (more detailed test requirements below)
(see http://www.redhat.com/security/updates/errata/ for RHEL support policies)
On all distros listed above the following will be tested:
| Test | Criteria |
|---|---|
| Clean install from native distro packaging (.deb on Debian, .rpm on Fedora/RHEL | No errors or obvious failures |
| Run SimpleTest automated tests | All tests pass or have well-documented exceptions |
| Upgrade from previous release | No errors or obvious failures, all existing data is maintained |
On the current Debian release the following will be tested in addition:
| Test | Criteria |
|---|---|
| Multi-system clean install from native distro packaging | No errors or obvious failures |
| Fedora distro analysis | No errors or obvious failures, spot-check the license analysis for errors |
Here are links to relevant documentation for testing FOSSology