REVIEW-30: SDIACT-234 Enhance Resource Prediction Service showing where jobs would run first - Test Readiness Review

The Karnak service primarily provides predictions of how long jobs will wait in queues on XSEDE systems before they begin to execute. Predictions can be requested for jobs that are about to be submitted or jobs that have already been submitted and are waiting in queues. SDIACT-234 is an incremental update to the Karnak prediction service to improve predictions and provide alternative response formats.

• (Peter) Confusing wording describing grouping and small typos
  • Fixed and new tests added to test plan
• (Peter, Choonhan) Karnak page needs introductory text explaining what Karnak is
  • This will be added after testing is completed.
• (Peter, Choonhan) Design document is incomplete
  • Because this activity was an incremental update and was done using the agile model, we did not do a formal design review. Thus the design document is rough and we will note in the final test report that it needs improvement in any future activities.

Documentation

• Introduction
  • http://karnak.xsede.org/karnak/index.html
• Design/Security overview
  • Security and General Design Description
• Installation guide
  • n/a (already deployed service)
• Deployment Plan
  • SDIACT-234 Deployment Plan
• User guide
  • Karnak page. Note that the user documentation here needs a better introduction and some examples. This will be done by the testers after testing has completed.
  • Karnak XSEDE16 Poster
  • Slides from June Gateway call
• Defect, issue, and risk reporting
  • Use message board to right during testing and help@xsede.org after testing.
• Acceptance test plan
  • Test Plan
• Testing resources
  • Stampede (Choonhan)
  • Comet (Peter)

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.