Group Overview
The Testing team lives on the edge! We not only like to break software, but also like to run beta releases in places where we probably shouldn't be running beta releases.
Software is complex and testing is an important part of doing battle with this complexity. When developing new software, it is easy to test and catch obvious problems in the lab (read: the downstairs couch). However, we all know that what works in the lab will not always work in the field. What happens when you have a system running with:
- 3 Internet connections
- Content filtering
- VPN connected to 10 remote offices
In theory, it should all work, right? All those features have been tested, but perhaps a corner case was missed.
Responsibilities
- Testing alpha, beta and release candidates
Wish List
Software Testing
A lot of bugs can be tested using standard test frameworks. For example, we can test that adding TCP port 88888888 to the firewall will indeed generate an error message. To date, ClearOS uses a number of ad-hoc test scripts. Ideally, some standard test frameworks should be adopted, for example:
