Test matrix
From Linux NFS
(Difference between revisions)
(Refactoring layout a bit) |
|||
Line 1: | Line 1: | ||
- | |||
- | |||
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! | 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! | ||
- | |||
- | |||
==[[Matrix_functional_section|Functional Testing]]== | ==[[Matrix_functional_section|Functional Testing]]== | ||
Line 28: | Line 24: | ||
|22 | |22 | ||
|} | |} | ||
+ | |||
==[[Matrix_interop_section|Interoperability Testing]]== | ==[[Matrix_interop_section|Interoperability Testing]]== | ||
Line 54: | Line 51: | ||
|25 | |25 | ||
|} | |} | ||
+ | |||
==[[Matrix_robustness_section|Robustness Testing]]== | ==[[Matrix_robustness_section|Robustness Testing]]== | ||
Line 80: | Line 78: | ||
|2 | |2 | ||
|} | |} | ||
+ | |||
==[[Matrix_performance_section|Performance Testing]]== | ==[[Matrix_performance_section|Performance Testing]]== | ||
Line 132: | Line 131: | ||
|9 | |9 | ||
|} | |} | ||
+ | |||
==Definitions== | ==Definitions== |
Revision as of 22:51, 19 May 2005
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!
Contents |
Functional Testing
Ability to do what it's supposed to do. Standards compliance, regression, compatibility, static code analysis, etc.
New | Open | In progress | Near Done | Done | High | Medium | Low | |
---|---|---|---|---|---|---|---|---|
current status | 104 | 26 | 1 | 1 | 4 | 43 | 72 | 22 |
Interoperability Testing
Ability to work with other versions of NFS, other operating systems and other software/filesystems/etc. generally associated with NFS
New | Open | In progress | Near Done | Done | High | Medium | Low | |
---|---|---|---|---|---|---|---|---|
current status | 55 | 12 | 0 | 0 | 1 | 33 | 12 | 25 |
Robustness Testing
Remains stable and recovers even in extreme situations, Stability, interoperability, error recovery, race conditions, etc
New | Open | In progress | Near Done | Done | High | Medium | Low | |
---|---|---|---|---|---|---|---|---|
current status | 43 | 4 | 1 | 0 | 3 | 32 | 8 | 2 |
Performance Testing
Able to perform well under real and theoretical workloads Load, stress, destruction, scalability, etc
New | Open | In progress | Near Done | Done | High | Medium | Low | |
---|---|---|---|---|---|---|---|---|
current status | 33 | 10 | 3 | 0 | 1 | 19 | 26 | 4 |
Matrix_security_sectionSecurity Testing
Resistant to being compromised and difficult to attack
New | Open | In progress | Near Done | Done | High | Medium | Low | |
---|---|---|---|---|---|---|---|---|
current status | 28 | 4 | 0 | 0 | 1 | 14 | 9 | 9 |
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