Test matrix

From Linux NFS

(Difference between revisions)
Jump to: navigation, search
(Category)
(Category)
Line 11: Line 11:
*'''[[Matrix_robustness_section|Robustness]]''' : Remains stable and recovers even in extreme situations, Stability, interoperability, error recovery, race conditions, etc
*'''[[Matrix_robustness_section|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
*'''[[Matrix_performance_section|Performance]]''' : Able to perform well under real and theoretical workloads Load, stress, destruction, scalability, etc
-
*'''[[Matrix_secutity_section|security]]''' : Resistant to being compromised and difficult to attack
+
*'''[[Matrix_secutity_section|Security]]''' : Resistant to being compromised and difficult to attack
= Status Summary =
= Status Summary =

Revision as of 22:40, 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.
  • Interoperability 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
  • 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

Interoperability Testing

New Open In progress Near Done Done High Medium Low
current status 55 12 0 0 1 33 12 25

Robustness Testing

New Open In progress Near Done Done High Medium Low
current status 43 4 1 0 3 32 8 2

Performance Testing

New Open In progress Near Done Done High Medium Low
current status 33 10 3 0 1 19 26 4

Security Testing

New Open In progress Near Done Done High Medium Low
current status 28 4 0 0 1 14 9 9
Personal tools