Test matrix
From Linux NFS
(Difference between revisions)
(→Robustness Testing) |
|||
(22 intermediate revisions not shown) | |||
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! | |
- | + | ==[[Matrix_functional_section|Functional Testing]]== | |
- | + | Ability to do what it's supposed to do. Standards compliance, regression, compatibility, static code analysis, etc. | |
- | + | ||
- | + | ||
- | = | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
{|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100% | {|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100% | ||
!style="background: #ececec;"| | !style="background: #ececec;"| | ||
Line 35: | Line 15: | ||
|- | |- | ||
|current status | |current status | ||
- | | | + | |102 |
- | | | + | |30 |
|1 | |1 | ||
- | | | + | |0 |
- | | | + | |5 |
|43 | |43 | ||
|72 | |72 | ||
Line 45: | Line 25: | ||
|} | |} | ||
- | ==Interoperability Testing== | + | ==[[Matrix_interop_section|Interoperability Testing]]== |
+ | |||
+ | Ability to work with other versions of NFS, other operating systems and other software/filesystems/etc. generally associated with NFS | ||
{|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100% | {|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100% | ||
Line 59: | Line 41: | ||
|- | |- | ||
|current status | |current status | ||
- | | | + | |57 |
|12 | |12 | ||
|0 | |0 | ||
Line 69: | Line 51: | ||
|} | |} | ||
- | ==Robustness Testing== | + | ==[[Matrix_robustness_section|Robustness Testing]]== |
+ | |||
+ | Remains stable and recovers even in extreme situations, Stability, interoperability, error recovery, race conditions, etc | ||
{|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100% | {|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100% | ||
Line 83: | Line 67: | ||
|- | |- | ||
|current status | |current status | ||
- | | | + | |29 <!-- It was 37 --> |
- | | | + | |6 |
- | |1 | + | |1 |
- | | | + | |2 <!-- add maximum files exported / mounted --> |
- | | | + | |6 <!-- tests ffsb/fsstress and IOZone running long periods (1 week) + disk limits on server/client maximum file size (=local fs)--> |
|32 | |32 | ||
|8 | |8 | ||
Line 93: | Line 77: | ||
|} | |} | ||
- | ==Performance Testing== | + | ==[[Matrix_performance_section|Performance Testing]]== |
+ | |||
+ | Able to perform well under real and theoretical workloads Load, stress, destruction, scalability, etc | ||
+ | |||
{|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100% | {|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100% | ||
!style="background: #ececec;"| | !style="background: #ececec;"| | ||
Line 106: | Line 93: | ||
|- | |- | ||
|current status | |current status | ||
- | | | + | |35 |
|10 | |10 | ||
- | | | + | |6 |
- | + | ||
|1 | |1 | ||
+ | |3 | ||
|19 | |19 | ||
|26 | |26 | ||
Line 116: | Line 103: | ||
|} | |} | ||
- | ==Security Testing== | + | ==[[Matrix_security_section|Security Testing]]== |
+ | |||
+ | Resistant to being compromised and difficult to attack | ||
+ | |||
{|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100% | {|border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100% | ||
!style="background: #ececec;"| | !style="background: #ececec;"| | ||
Line 138: | Line 128: | ||
|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 |
Latest revision as of 09:25, 14 November 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 | 102 | 30 | 1 | 0 | 5 | 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 | 57 | 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 | 29 | 6 | 1 | 2 | 6 | 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 | 35 | 10 | 6 | 1 | 3 | 19 | 26 | 4 |
Security 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