REVIEW-60: XCI-186 Usage and error reporting enhancements for xdusage - Test Readiness Review

The xdusage command-line tool reports allocation information for a given user such as total SU awarded as well as SU's used and remaining for each of their allocations.  XCI-186 delivers xdusage 2.1, which improves error reporting during installation and configuration.

• (Derek) User doc referenced old CTSSv4 module
  • Peter submitted help ticket and got the doc updated to use 'xdusage' instead
• (Christopher) Test instructions say the the api_id field in the xdusage.conf file should be set to some unique client machine name or user name that is NOT the resource_name but install instructions say different.
  • Peter says for testing that is recommended and should not cause a failure

• Design/Security overview
  • Security and General Design Description
• Installation guide
  • XCI-186 Installation Guide
• Deployment Plan
  • XCI-186 Deployment Plan
• User guide
  • Guide
• Defect, issue, and risk reporting
  • See XCI-186 test plan below 
• Acceptance test plan
  • Test Plan
• Testing resources
  • (Christopher) racd.xsede.org - CentOS 6 - RPM
  • (Derek) - ?? - CentOS 7 - Tar.gz

• Design/Security overview
  • Security and General Design Description
• Installation guide
  • XCI-186 Installation Guide
• Deployment Plan
  • XCI-186 Deployment Plan
• User guide
  • Guide
• Defect, issue, and risk reporting
  • See XCI-186 test plan below 
• Acceptance test plan
  • Test Plan
• Testing resources
  • (Christopher) racd.xsede.org - CentOS 6 - RPM
  • (Derek) - ?? - CentOS 7 - Tar.gz

Package information: All software packages (e.g., server and client packages) for this CI are listed.

Documentation and Installation instructions: The deployment plan for this CI on XSEDE is clearly described as well as the installation instructions and any XSEDE specific configuration instructions.

Test environment and facilities: The test environment needed to adequately to validate this component is described. Should indicate also whether testing can be performed within a VM and if not, the reasons for it.

Assumptions: Lists any assumptions needed before testing can begin (e.g., accounts needed).

Test procedures, cases, and scenarios: Lists the tests that should be run or an associated test suite and expected performance metrics if applicable.

Defect, issue, and risk reporting: Deployment plans should include defect and issue reporting information. The testing plan could reference that same information from the deployment plan, or provide alternate information if defects and issues need to be reported differently during testing. Risks, as well as defects and issues, should be part of the testing report.