1. “Kuality” Assurance What does that look like? Scott Heise Indiana University KFS - Quality Assurance Manager Kenton Hensley Cornell University KRA – Lead Business Analyst

2. Introduction What is Quality Assurance? –The set of techniques and procedures used to assure timely delivery of the software that meets specified requirements.

3. Introduction What are the benefits of QA? –Improved utilization of time and resources –Improved control of quality and processes –Consistent quality and timely delivery –Increased stakeholder satisfaction –Lower rejection rates, rework, and implementation costs –Improved performance of software –Improved control during periods of change or growth

4. Scott Heise Indiana University Kuali Financial System (KFS) Quality Assurance Manager

5. “Kuality” Assurance

6. Automated Unit Testing

7. Unit Testing First line of defense Automated Errors and failures are addressed quickly

8. Manual Testing

9. Test Plans based on Functional Specs SME/User Testers from many institutions

10. Testing

11. Code Review

12. Accessibility Review

13. Accessibility Guidelines Test by sampling “Issues” approach to resolution

14. License Review

15. Licensing Software distribution licensing –Open Source Initiative (OSI) Educational Community License 2.0 (ECL) Original code –Individual Contributor License Agreements (CLAs) –Corporate Contributor License Agreements (CCLAs) –© Labeling the code Third-Party code –ECL-Compatible License –Follow license requirements –Acknowledgments –License folder

16. Quality Assurance Framework

17. KFS Testing/Usability

18. KFS Team Organization

19. Testing Structure Testing Teams –One per module –Module Testing Coordinator Write/assign scenarios to testers Train testers on Kuali, Confluence, JIRA Review Bugs: Duplicate? Training? Usability? –Testers from all schools – 15 plus/module KFS Testing Coordinator –Monitors issues application wide –Assists Module Testing Coordinators

20. Tools - JIRA

21. Tools - Confluence

22. Testing Process eDoc/process ready for testing Scenario created/assigned – JIRA Bugs reported in JIRA Issues fixed marked as resolved Testing environment released weekly Release notes created - Confluence Testers test close/reopen Rinse and Repeat!

23. Usability – Before Coding Indiana UXG – Usability Group –Developed Standards/Guidelines for the UI –Initial Mocks reviewed by Kuali Financial Functional Council Decisions made: –Editable data entry lines –Page Level Help – no field level help –Usability sessions with users from each school via Breeze

24. Usability – During/After Coding Marked as Usability Reviewed and Prioritized by Usability Prioritization Committee Usability Development team formed during the QA Period Usability issues that affect infrastructure, reviewed and time allocated during next release, e.g. – error handling framework

25. Quality Assurance Period

26. 3 months of QA QA Period begins with a freeze on new functionality 2 months are dedicated to finding and fixing bugs The final month is intended to achieve stability prior to release

27. Lessons Learned Training for testers Pre-Testing to ensure a fairly stable environment Weekly meetings with testers Face to Face sessions Never too many testers Testing is the BEST way to learn! Plan a sufficient QA Period

28. Questions?

29. Contacts Please feel free to contact the following individuals about the KFS, KRA or Coeus projects: Jim Thomas, Project Manager Indiana University – jthomas@indiana.edu Andy Slusar, Senior Project Manager Cornell University – as833@cornell.edu Steve Dowdy, Director of Electronic Research Administration MIT – sdowdy@mit.edu