bowdenj
commented
6 years ago Notes from meeting: Participants: Katya, Jasmine, Shaylee, Jason R, Audrey, Imran
In the future, the team would like to see:
- A timeline for testing approximately two+ weeks out, with dates for when testing will be available and proposed names for dashboard testing PoCs. This way, testing PoCs can assign backups.
- Include a meeting that walks through at least one example dashboard to test to show the best way to catch, document, and report errors to the development team.
- Put together PoCs for each dashboard ahead of time. This way, we will consistently have testers matching up with their experience/dashboards they are familiar with.
- Include a list of items that changed so testers know specifically what to look for.
- For every ticket or enhancement update, there should be a point of contact for clarifying questions.
- SIMS: Could not perform a direct comparison of CEE results because there was no test SIMS dataset. For SIMS testing, there needs to be a test dataset (similar to the MER test dataset) for at least one or two OUs.
- It would be helpful for ICPI testers to know what the developers test for compared to what ICPI testers need to look for specifically, to make sure there is no duplication of effort or gaps.
- As we move forward into Q3 and move from Report Builder to Dossier, what implications will that change have on our testing process? Will checks be different? This will be important to keep in mind as we move towards Q3 close in August.
jb3436
pvinayak001
Hi @jb3436 @shapaklyak @shazadahmed10 @aliyahwakil @mehtasp @kimisatoPC @KatieOC @pvinayak001 @cnichols3h @bbaack @MicSherlock @HoustonJamie @imujawar - and any others who are interested:
Thank you all so much for the testing you did over the past few days in preparation for the Pano release. Thanks to your testing, we had over 27 issue reports (and many of those reports included a variety of distinct issues). Ultimately, the Pano development team was able to correct all but four issues, and all four are on the list for potential fixes in the June 1 fast-follow. Please see the attached list of issues reported for this release (the top four rows are the ones that were ultimately not resolved). Issues Tracker Q2_v0522_v2.xlsx
The timeline for Panorama testing is always tight due to when the data comes into the development site from DATIM and the standing release deadlines. However, we would like to hear from you if there is anything that we can do next time to ease this process for you. Next time, we'll certainly provide more advance notice for testers. What else can we do to ease the process? Any feedback about training, methodology, test datasets, communications, or other topics are welcome.
I'd like to take a few minutes to discuss this at the next DIV meeting, but in the meantime, feel free to share your thoughts or brainstorm here. Thank you!