Testing - non-functional tests » History » Revision 2
Revision 1 (Ivo Jimenez, 06/13/2015 09:31 AM) → Revision 2/5 (Ivo Jimenez, 06/13/2015 10:25 AM)
h3. +*Non-Functional Tests*+ *Summary* For Please provide a particular hardware and cluster setup, we can reasonably expect some baseline behavior from Ceph. brief description of this blueprint. For example, that it scales linearly, or that it has a certain availability properties. "Non-functional testing":https://en.wikipedia.org/wiki/Non-functional_testing refers convenience, try to this type of tests write something short and this blueprint proposes their addition. easy to understand. *Owners* This is mandatory. List of the owners for this blueprint, along with affilition (if appropriate). Chances are good that this list should include your name! Ivo Jimenez (UC Santa Cruz / RedHat) *Interested Parties* If you are interested in contributing to this blueprint, or want to be a "speaker" during the Summit session, list your name here. Ivo Jimenez (UC Santa Cruz / RedHat) *Current Status* There Please describe the current status of Ceph as it relates to this blueprint. Is there something that this replaces? Are there current features that are currently only functional tests in the code base (AFAIK). related? *Detailed Description* This is the big one! Please provide a detailed description for the proposed change. Where appropriate, include your architectural approach, a list of systems involved, important consequences, and issues that are still unresolved. *Work items* This might be doable section should contain a list of work tasks created by adding new teuthology tests that check high level assertions. It might require the execution of some benchmarks this blueprint. Please include engineering tasks as well as related build/release and checking validations over the output data of such benchmarks. At UCSC, we have developed a tool to codify and check documentation work. If this type blueprint requires cleanup of validations called "Aver":https://github.com/ivotron/aver . Aver provides a language that can be used to express validation statements against performance metrics. Check our "tech report":https://www.soe.ucsc.edu/research/technical-reports/UCSC-SOE-15-07/download which includes an example of testing the scalability properties of Ceph. deprecated features, please list those tasks as well. *Work items* *Coding tasks* Either integrate Aver or implement another validator over benchmarking output data Task 1 Define tests for particular setups: scalability, recovery, performance Task 2 Task 3 *Build / release tasks* Task 1 Task 2 Task 3 *Documentation tasks* Add documentation on how non-functional testing works in Ceph (either teuthology) Task 1 Add instructions on how to add new tests Task 2 Task 3 *Deprecation tasks* Task 1 Task 2 Task 3