Test matrix

From Linux NFS

Revision as of 20:50, 13 June 2005 by BryceHarrington (Talk | contribs)
Jump to: navigation, search

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 100 30 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 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 33 10 3 0 1 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
Personal tools