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.
Review Input Documents
- Design/Security overview
- Installation guide
- n/a (already deployed service)
- Deployment Plan
- User guide
- Defect, issue, and risk reporting
- Use message board to right during testing and firstname.lastname@example.org after testing.
- Acceptance 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.
ScheduleCurrent Date: 2019-02-22
Current Status: Closed (Test Readiness Review)
|Target Date||Actual Date||Activity Milestone|
|2016-08-16||Review launch date|
|2016-08-23||2016-08-26||Written feedback due (Reviewers)|
|2016-08-17||2016-08-30||Written response date (Review Material Developers)|
|2016-08-18||2016-09-21||Final approval due and completion date (Reviewers)|
Review Last Updated: 2016-09-21 10:30 am
If you are a reviewer, please login to sign or withdraw from this review.
- Peter Enstrom
SIGNED: 2016-08-18 09:00
- Shava Smallen
SIGNED: 2016-08-22 13:32
- Choonhan Youn
SIGNED: 2016-08-18 14:25
- Marlon Pierce
- Gary Rogers
SIGNED: 2016-08-24 14:16
Review Material Developers