HUIT Development Standardization Project Quality Assurance Committee Kickoff Meeting Greg Roy, Joseph Hardin | 10/31/2013 Agenda • Introduction • Discuss Goals of the Committee • Roles and Responsibilities • Review Current State • Discuss Next Steps – Populating a dictionary of terms – Documenting test-writing methods – Document Bug reporting details 2 INTRODUCTION 3 Standardization Project Goals • Enable people to work across boundaries and across HUIT • Allow new people to quickly ramp-up and be productive • Free up developers from redundant administrative tasks to allow them to focus on development and innovation • Simplify interaction between developers and support (SOC, release management, DAAG) • Recommend solution for HUIT, but also collaborating with CTO as he defines standards for the University to ensure that we get a cohesive solution • Convene multiple committees on different topics – Version Control – Bug Tracking – Enterprise Architecture – Software Development Practices 4 Quality Assurance Committee Goals • Dictionary of terms – Test Plan/Case/Steps? – Driven by management tool? • Collection of Test writing methodologies – Recommendations as to when to use what ones – Ways to collect necessary data • Standard way to report bugs/issues – Terms, steps, – Tool used • Metrics – Recommendations, how to use, etc. 5 Quality Assurance Committee Goals • Test Case Management standardization – Tool based? – Term based? – This could lead to a unified tool recommendation • Automated Testing – Functional • Gui driven (Selenium, HP Suite, others?) • Code Driven (unit testing – QA assistance to devs) – Performance • Gui Driven (Selenium, others?) • Network Packet Driven (jMeter, HP Performance Center) – This could lead to a unified tool recommendation 6 Quality Assurance Committee Goals • Certifications – Identify different options – Make a recommendation towards a specific one 7 Quality Assurance Committee • Schedule – 3 scheduled committee meetings, may need to add one or two more – Recommendation created by mid - late January • Homework – Type varies each meeting week • Populating a unified dictionary, Researching methods, trying new tools, etc. – Outreach to your local groups • Outcome – Recommendation to the Steering Committee regarding results and potential tool recomendations 8 Meeting Agendas • Review current results of assigned homework – Additional discussion • Identify next items to work on 9 Discuss COMMITTEE GOALS 10 Introduce ROLES AND RESPONSIBILITIES 11 Roles and Responsibilities • Committee Members – Attend meetings – Engage as an active participant in discussions and decisions – Communicate with local groups, bringing ideas into the meetings and disseminating information from them – Evangelize to local groups, encouraging them about the process – Some “homework” (1-2 hours/week) • Committee Chairs – Same as Committee, plus facilitating meetings 12 Review CURRENT STATE 13 Current State of Quality Assurance in HUIT • Developer Ratio 14 12 10 8 6 QA Developer 4 2 0 14 Current State of Quality Assurance in HUIT • Product Ratio 25 20 15 10 QA Products 5 0 15 Current State of Quality Assurance in HUIT • Tools Used Automation functional or performance Test Case Management Bug Tracking Selenium IDE Excel Jira Selenium Web Driver Jira Remedy jMeter Zephyr Bugzilla HP Performance Center 16 Discuss NEXT STEPS 17 Homework • Log into the confluence site and start populating / adding to the dictionary – https://wiki.harvard.edu/confluence/display/SQSP/HUIT+Software+Qualit y+Standardization+Project+Home • Select a test-writing methodology or two from the posted list and research, write up a description on the site • Document how you report bugs for discussion comparison at next meeting – If using an application (Jira, Bugzilla): fields used vs fields offered. – How you label each section of a bug report – Etc. 18 HUIT Quality Assurance Standardization Project Joseph Hardin, Greg Roy October 31, 2013