Test matrix
From Linux NFS
(Difference between revisions)
(→Functional Testing) |
|||
| Line 44: | Line 44: | ||
<td>1</td> | <td>1</td> | ||
<td>4</td> | <td>4</td> | ||
| - | |||
<td>43</td> | <td>43</td> | ||
<td>72</td> | <td>72</td> | ||
Revision as of 08:10, 19 May 2005
Version 1.12
This pages summarizes testing efforts for NFSv4, and identify testing gaps. Email nfsv4@linux-nfs.org with feedback or to take ownership of a task. If you are doing NFSv4 testing, please let us know! The matrix is divided into five categories, each on its own page in this page.
Contents |
Category
- Functional Ability to do what it's supposed to do. Standards compliance, regression, compatibility, static code analysis, etc.
- interop Ability to work with other versions of nfs, other operating systems and other software/filesystems/etc. generally associated with NFS
- Robustness : Remains stable and recovers even in extreme situations, Stability, interoperability, error recovery, race conditions, etc
- [Matrix_performance_section|Performance]] : Able to perform well under real and theoretical workloads Load, stress, destruction, scalability, etc
- security : Resistant to being compromised and difficult to attack
Status Summary
Definitions
- New : An owner has not been identified for the item and work has not started on it
- Open: The task has been adopted, but either has not been started, or progress is not yet known
- In Progress : Some work has been completed on the task
- Near Done: The principle essense of the task has been finished, but there are some loose ends left
- Done: The task has been fully completed
Functional Testing
| New | Open | In progress | Near Done | Done | High | Medium | Low | |
| Current status | 104 | 26 | 1 | 1 | 4 | 43 | 72 | 22 |
