REVIEW-68: XCI-566 Testing of xdinfo 1.4

The xdinfo command line tool allows users view information from XSEDE central information services from the command line.  Version 1.4 enables xdinfo to work with Python 3.

Documentation

• Introduction
  • See short user guide below
• Design/Security overview
  • Security and General Design Description
• Installation guide
  • Xdinfo Installation Guide
• Deployment Plan
  • XCI-566 Deployment Plan
• User guide
  • xdinfo user guide
• Defect, issue, and risk reporting
  • See XCI-566 test plan below
• Acceptance test plan
  • Test Plan - Run the test plan with Python 3 and 2.7
• Testing resources
  • CentOS 7 resource

Documentation

• Introduction
  • See short user guide below
• Design/Security overview
  • Security and General Design Description
• Installation guide
  • Xdinfo Installation Guide
• Deployment Plan
  • XCI-566 Deployment Plan
• User guide
  • xdinfo user guide
• Defect, issue, and risk reporting
  • See XCI-566 test plan below
• Acceptance test plan
  • Test Plan - Run the test plan with Python 3 and 2.7
• Testing resources
  • CentOS 7 resource

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.