FVT Process

FVT Scope Describtion:

The following are typical focus areas in any FVT/FVT-R test phase.

• Install/Uninstall/Re-Install/Upgrade/Migrate
  Release-to-Release Interoperability Testing
  Regression Testing
  Authorization, Authentication, and Security
  Backup and Recovery
  Graphical User Interface (GUI) Testing
  APIs (Including REST APIs)
  Command Line Testing
  Help Testing (Includes GUI help, command line help (man pages, -h, - -help), and review of Info Center)
  Error injection and Recovery Testing
  IP Network Communication Protocols
  Databases supported by the product
  LDAP (Configure the Director Server to use LDAP and verify commands/GUI function correctly)
  Event actions/responses
  Logging and tracing levels and files
  Dump files (verify correct dump files were generated)
  Audit records are created and logged as documented
  File/Directory permission's and ownership
  FFDC
  Cross Platform Testing
  Limits and Boundaries
  Use Cases
  Globalization Verification Testing (GVT)
  Accessibility Verification Testing (AVT)
  Artistic (Free Form) Testing (FVT Teams should create test cases for artistic testing to ensure this valuable testing is done.)
  New Hardware Compatibility
  New Software Compatibility (Operating System, Firmware, Databases)

Execution:

The following are typically not covered by FVT:

• Unit Test activities for individual modules, verification of all code paths, etc.
  Build Verification Test (BVT)
  System Verification Test (SVT)
  Reliability, Availability, and Serviceability
  Performance testing
  Scalability testing
  User Centered Design (UCD) testing
  
  
  Note:FFDC;First failture data capture