Main Page
From Linux NFS
(Difference between revisions)
m (despamming) |
|||
Line 28: | Line 28: | ||
'''Testing''' | '''Testing''' | ||
* [[Testing tools]] | * [[Testing tools]] | ||
+ | * [[Emulating tools]] | ||
* [[Functional testing]] | * [[Functional testing]] | ||
* [[Interoperability testing]] | * [[Interoperability testing]] | ||
Line 35: | Line 36: | ||
* [[Tests needed]] | * [[Tests needed]] | ||
* [[Testing methodologies]] | * [[Testing methodologies]] | ||
- | * [[Test_matrix| | + | * [[Test_matrix|Test matrix]] |
* [[Testing forecast roadmap]] | * [[Testing forecast roadmap]] | ||
|} | |} |
Revision as of 13:10, 3 October 2005
NFS is a critical service in many organizations, and even a simple error can lead to major problems. NFSv4 promises to bring several key new features, but clearly it will be imperative to users that the new version of NFS be robust, that it perform well, and that it interoperate easily with other technologies.
General |
Troubleshooting
|
Testing |
Testing
The Linux NFSv4 Testing effort seeks to ensure that the Linux implementation of NFSv4 succeeds on all these counts. The purpose of the testing is threefold:
- To prove that the features are implemented correctly according to spec.
- To locate and identify bugs, and verify the fixes.
- To give confidence to users that upgrading to NFSv4 on Linux is of benefit.