<scribe> scribe:shimizuyohta
<jongund> https://github.com/w3c/aria-at/pulls
Michael: I'll do "added csv file for generating checkbox tests" by this weekeend.
Matt: Have some ideas about
readme section.
... Some points, project needs to be more welcoming for
newcomers, and planning to add that element.
... You can merge #129 130, Simon.
... Did you take the code from APG repo Jon?
Jon: Pretty much so, I made some changes. Updating this menubar example for practices for triggering update menubar for APG.
Matt: For #128, thing we want to make sure is it gets reviewed as part of APG project.
Jon: There's only 3 csv files, all the rests are individual test files.
Matt: There's 2 kinds of reviews.We do wanna make sure that this setup scripts code are made in consistent way. So I think some level of code review is needed here.
Simon: I agree. Also we should
change how we gets the example from APG. Currently it's
manual.
... I think it'd be better to have scripts to take all the
examples from APG.
Jon: There's gonna be problems with html files, cuz this is relative reference.
Matt: Longer term idea here is all the tests for ARIA-AT would go into a test directory for APG repo.
Jon: So reference should be takend out of this?
Matt: Examples are test cases.So we could make directory called "example"
Jon: Or could just url to APG and point to them
Matt: Simon, can you lead the code review that are in the test sub-directory?
Simon: Yes, I can do that tonight and merge them.
Jon: Current place of code references is not good.
Matt: Let's make it a separate
issue.
... For #124, I'll let Simon look into it.
... #115 isn't ready, so we don't want to merge that.
Michael: I have script
ready.
... I'm gonna include the link. Should I point that link to a
specific version of APG, or unversioned URL
Matt: Editor's draft sounds
reasonable.
... That could be useful for APG project as well.
Michael: Got it.
Matt: Tricky part is generating a set of URL for all the examples, but I'll figure it out.
Simon: From what I'v heard from previous conversation, we can change to must have/should have.Question is coming to change test plan.
Matt: Make it optional may be
simpler, but wanna hear thoughts from CG.
... "Required" and "Optional" is the consensus by CG.
Jon: For scripts, default is 1.
If you wanna change, you add numbers.
... I can change scripts to make it two-state options.
Matt: Only changes to csv about
this is assertion priorities.
... So this means prototype needs to be updated Simon.
Simon: I'll write an issue to prototype.
Jon: In the prototype, there's help references and link.What are they gonna be used for?
Simon: I don't think there's particular purpose other than pointing where examples come from.So it's not required.
Jon: Combobox doesn't have help
reference, but other examples has those.
... How important it is my question.
Matt: One of the thing we wanna
be able to do is a query to report for all tests of particular
attributes.Everything related to aria-chached/checkbox role,
etc.
... I don't know well enough to definitively say that. But it
makes me wonder those keys are specific enough. Help doesn't
seem right.
Jon: Okay,I'll link to ARIA role/attribute for now.
Matt: Are these links to ARIA specs to the APG? Are these links to data that enables us to associate with attributes in APG?
Simon: I'll create the issue for that.
Matt: We do need a way of making sure test is directly associated with correct tests.
Jon: One issue is I have csv file
called "references".
... But sounds like we shouldn't have it in a separate
file.
... Only use for "reference" file for now is to point out to
pracitices and examples.
Isaac: I have posted an issue
about wireframe.My next step is to update the use cases.I'd
like to get feedback for these two pieces.
... I've been working with four use cases.
<zcorpan> https://github.com/w3c/aria-at/issues/132
Isaac: Isuse is #132
... Describing high-level structure of wireframe.See link above
for detail.
... There's executing a test page, from tester's
perspective.
... In this wireframe I have 3 tests.From this page, idea is
testers will see who is assigned to every of this tests.If no
one is assgined, they can assign themselves.
... As soon as someone is assigned, that tests is taking away
from everyone else, except the tester.
... E.g. I'm tester and see Valerie assigned, I can assign
myself. > That'll be taking the test from everyone else.
Matt: Each row in the table is test run, correct?
Isaac: Not for now, so we might need to change that.
Matt: Yes, I don't think tester
will go that granular.
... We wouldn't wanna list all the 6 test here.
Isaac: The way I have for now is
I have 3 tests. Each of test have 6 different AT/browser
combination.
... Don't we need granurarity of AT/browser, assuming testers
who can only use a specific AT/browser combination?
Matt: There should be 6 rows of
checkbox, not 96.
... For checkbox for current test,there should be 6 runs of
checkbox plan for AT/browser combination.
Isaac: When I say test, I'm referring to an individual test.
Matt: We wanna assign whole run
for a person.
... Maybe we should call it as test plan run.
Simon: I'll change the vocabulary in the wiki accordingly.
Matt: That way, one column could be test run name/browser/AT/assignee.
Simon: We also have progress column.
Matt: You could give overall summary of test run plan.
Isaac: I'll update that this weekend, and I think we should have dedicated meeting on wireframe and usecases by next week.
Matt: Can you send the list beforehand so that people can preview.
Isaac: If everyone can preview,
maybe we don't use entire meeting time.
... We'll email everyone once it gets ready.
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: Matt_King, zcorpan, Joe_Humbert, shimizuyohta, jongund, isaacdurazo, michael_fairchild Present: Matt_King zcorpan Joe_Humbert shimizuyohta jongund isaacdurazo michael_fairchild Found Scribe: shimizuyohta Inferring ScribeNick: shimizuyohta WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]