Quality Assurance for Coeus and Kuali Coeus Kuali Coeus User Group 2011

1. Quality Assurance for Coeus and Kuali Coeus Kuali Coeus User Group 2011

2. Quality Assurance for Coeus and Kuali Coeus • Kyle Burkhardt Princeton University Coeus Coordinator • Jon Peterson Colorado State University KC QA Technical Lead • Jen Flach Jenistics LLC Coeus/KC Quality Assurance Manager

3. Objectives Learn How To: Approach upgrade testing your institution Leverage project-level QA resources Report bugs found locally Contribute bug fixes to KC

4. Coeus Upgrade Testing at Princeton University

5. Coeus/KC Project QA Resources • Web-based Project Tools: • Confluence (wiki) • JIRA (bug tracking) • Contour (test scripts) • Reporting a bug found locally • KC bug fix contribution

6. QA Resources: Confluence (wiki) • Wiki – information management • Project teams, Subcommittees • Functional & Technical specifications • Quality Assurance resources, procedures, FAQs KC: https://wiki.kuali.org/display/KRACOEUS/Kuali+Coeus+Functional+Home https://wiki.kuali.org/display/KRACOEUS/Kuali+Coeus+Quality+Assurance+Home+Page Coeus: https://wikis.mit.edu/confluence/display/COEUS/Test+Scripts+from+Coeus+Schools

7. Confluence (wiki) – KC

8. Confluence (wiki) - Coeus

9. QA Resources: JIRA (bug tracking) • Bug tracking system • JIRA review, disposition & prioritization process • Linking & Filtering back to Confluence • Issue Status pages • https://wiki.kuali.org/display/KRACOEUS/KC+QA+Release+3.1+All+Resolved+Issues

10. JIRA (bug tracking)

11. JIRA Linking/Filtering in Confluence

12. QA Resources: Contour (test scripts) – KC • Requirements • Functional • Design • Test Analysis • High-level test cases • Test Scripts • Detailed test steps

13. Contour: Requirements

14. Reporting a bug: Before creating a new JIRA • Reproduce locally – ensure it is a bug • Retest in another local instance, if available • Determine specific steps, data, etc. that trigger the bug • Verify against user documentation and other resources • See if the bug has already been reported  • Look in COEUSQA or the relevant KC JIRA projects • Retest in Coeus Consortium QA or KCTRUNK environment • May confirm the issue persists in later release • Provides information for troubleshooting if the same steps produce different results

15. Reporting a bug found locally: Key fields • Affected version(s) – release(s) in which bug was found • Details on the local environment:  • Code table, parameter, and other set up • Server, database, OS, java, browser versions • Production and/or test environment? • Description of bug • Step-by-step • Screen shots • Log files • Test data (be careful not to share anything confidential) • Any troubleshooting attempts and workarounds

16. KC Bug Fix Contribution Process • Based on existing processes • Modeled after KFS procedure • Similar to Coeus approach • Managed using JIRA • Posted in Kuali Confluence: • KC Contributed Code Process • Formal process of contributed code: • Kuali Contributions Guide

17. KC Bug Fix Contribution Process • “Trusted” partners contribute lightweight Bug Fixes to KC • Trusted partner = Staff of an investing partner institution or organization with proven experience developing KC code • Provides mechanism to: - contribute back fixes made locally - work lower-priority bug fixes into a release

18. Project Resources • Collaboration Lists: • Coeus: COEUS@lists.rochester.edu • Kuali: https://wiki.kuali.org/display/KRADOC/Home • Help contacts: • help@coeus.org • help@kuali.org

19. Questions / Comments?