Test matrix

From Linux NFS

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 1 Functional Testing 2 Interoperability Testing 3 Robustness Testing 4 Performance Testing 5 Security Testing 6 Definitions

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