Meeting minutes
Matt_King: I want to discuss the sequence of events which need to happen in order for testing to begin again
Resumption of testing
Matt_King: We want to get as many of the test plans as we can in the new format through "draft review" and into "candidate review"
Matt_King: We want to prioritize "command button", alert, link, and radio group (prioritized in that order)
Matt_King: We can't run the tests, yet, but we're going to talk about the things that need to happen in order to get to the point where we can run the tests
Matt_King: As of this morning, the pull request which enables us to preview the new test plans in the ARIA-AT repo (not in the ARIA-AT app) is merged
Matt_King: ...so that means that we can work on the pull request for the refactored button, link, alert, and radio group
Matt_King: We can preview them using the preview feature in the pull request and the local preview
Matt_King: That part of the work is done
Matt_King: My question for howard-e is: I assume that we don't want to merge them into the "master" branch until the "import" feature (aria-at app #838) is merged. Is it correct that it would be a problem if we tried to merge sooner than that?
howard-e: You will have to merge at least on in order to test on sandbox
howard-e: There's a pull request (#998) which has all updated test plans. We're planning to merge that to sandbox. Doing so will circumvent the need to push to the "master" branch directly
howard-e: But it will not cause a problem if we merge some of those to the "master" branch. The version in production would not be updated because it will fail to import the new v2 test plans
Matt_King: That means the pull requests we already have for those test plans--IsaDC should be able to preview them, now, and make any changes
howard-e: Just to clarify: you will need to merge in the latest changes from "master" into the pull request branches
present James_Scholes
James_Scholes: we can close the existing pull requests and open new versions that are based on the latest
Matt_King: I will handle the two that I'm already managing
James_Scholes: So we have six to make "version 2 ready"
Matt_King: Just tell me when they're ready for me to review
IsaDC: This probably won't be ready by end-of-day Friday
Matt_King: But it seems like we should be ready in time for next Wednesday's meeting of this group
James_Scholes: We will aim for that, but I can't guaruntee that they will all be in a merge-able state by them.
Matt_King: The only one with any complexity here is "radio group."
Matt_King: The manual changes are basically: references, assertion priorities, and then just making sure that there weren't any commands that were doing the same thing but were worded differently
Matt_King: I think the first four will only take 15 to 20 minutes
James_Scholes: Yup. I'm hopeful we can, but our other obligations together with the complexities of "radio group" could impact the delivery schedule
Matt_King: So, by Wednesday, we could have some plans in the "master" branch
Matt_King: The next question is: when will it be possible for community group members to run tests?
Matt_King: My understanding is that there are two pieces of work which need to be deployed to production
Matt_King: Those are the importer and the test runner. I think they're currently represented in one pull request.
howard-e: That's right
Matt_King: If I reviewed that by Monday (along with the other reviews you've requested), would it be possible to plan a deployment for Monday?
howard-e: That should be possible
Matt_King: That would mean that by Wednesday's meeting, we would have some plans for folks to begin running and reporting data
Matt_King: Then it's a matter of lining up people to run tests, which we could hopefully start Wednesday of next week
murray_moss: I may be able to run tests after Wednesday of next week. I'll be at next Wednesday's meeting
Matt_King: Cool! Then we'll be able to assign some Test Plans to you at that time
James_Scholes: I will have bandwidth by Thursday of next week, provided that we're able to complete those pull requests in the mean time
James_Scholes: we may also be able to find someone else at PAC to run the tests