- Supported web browsers
- Security Assessment
- Who is the Testing Coordinator
- What is the Implementation Planning
Open Work:
- Email flow chart – Amber
- High-level write up for reporting – Amber
- Uses Cases / Test Cases – Amber
- High-level cases can be created, but others have to wait for the Dev upload and then promotion of Dev to QA.
- Create Scripts & Test – Ron / JP
- Four dependencies: Requirements to Test, Creation of Test Cases, Environment Availability and Time (QA to Prod is 10 Days and includes training and UAT)
- QA Test Strategy – Ron/Amber
- Create a new test ID – JP
- Create a new EGA to feed a new JIRA project for this upgrade – Benoit
- The EGA will be used for user to submit questions, concerns, feedback during testing and implementation.
- Each email will create a JIRA case.
Questions:
Customer Satisfaction Process – Out of the Box? – CIT HelpDesk Requirement
(Legacy process will not be carried over to the new system.)
What will be used for User Acceptance Testing?
(BMC's template, once appropriate for our modules, has about 5 things to be tested)
Per BMC's End User Testing Guide (page 3 under Training) "Testers should be trained on usage of the system before they begin testing".
In earlier meetings about this upgrade it was discussed that the Categorization hyperlink would either be moved to the Quick Action menu or as a tab alongside Work Details/Relationships/Date System.
(Currently it is hidden under the Links dropdown menu)
Who are the "Trainers" for each department? Have they been communicated to as to what this means and when?
(I assume these individuals will be participating in the User Acceptance Testing.)
What training material will be used?
(BMC's material is a PDF file containing 200 plus pages. It includes modules we are not implementing)
