REVIEW-70: XCI-419 Gateway attribute submission improvements for 2018 - Test Readiness Review

XSEDE requires all gateways to report the number of unique users per quarter who have executed jobs on XSEDE resources. This is a key metric that XSEDE in turn reports to the NSF. Compliance with this requirement justifies XSEDE's investment in the science gateway community. XSEDE has previously collected this information using a gateway attribute submit command-line tool that SPs install.  This activity delivers a new gateway attribute submit API that enables science gateways to directly submit the needed job attributes and does not rely on a SP installed command-line tool. 

This test readiness review is a lightweight review of the written materials and will then be followed by testing (of the proposed test plan).

Documentation

• Design/Security overview
  • Security and General Design Description
• Installation guide
  • n/a
• Deployment Plan
  • XCI-419 Deployment Plan
• User guide
  • User documentation (please ignore the colors -- this doc will be moved during deployment and the colors indicate new/moved text)
• Defect, issue, and risk reporting
  • See XCI-419 test plan below
• Acceptance test plan
  • Test Plan
• Testing resources
  • Any machine with a curl client

Documentation

• Design/Security overview
  • Security and General Design Description
• Installation guide
  • n/a
• Deployment Plan
  • XCI-419 Deployment Plan
• User guide
  • User documentation (please ignore the colors -- this doc will be moved during deployment and the colors indicate new/moved text)
• Defect, issue, and risk reporting
  • See XCI-419 test plan below
• Acceptance test plan
  • Test Plan
• Testing resources
  • Any machine with a curl client

Documentation and deployment instructions: The deployment plan for this CI on XSEDE is clearly described as well as the user 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: Test plans should include defect and issue reporting information. T