script: Yohta

TOPIC 1 : Prototype of testing contract

Matt: We briefly discussed prototype of testing contract last week.
... We had a conversation with some of the testing company. 4-5 days of start-up phase and discuss overview of the project such as goal, timeline.
... Probably invite potential testers to this meeting, and have them come up with some time of proto type in 5-6 week.

script: shimizuyohta

Michael: Liked that approach.

JF: Few questions. If we employ one person, what kind of skill we expect?

Matt: We expect person with engineer background who had experience in developing simular system.
... There was a group called bocuap, which done the simular project called, like test engineering, test management, designign test system.
... I don't want you to feel the burden of design is all on you JF. Ideally, if you feel you more need for design, please raise flag so that we can allocate more resources.

JF: That answers my concern.

Matt: Next week I'll bring back actual start date.

Issue #6, Design a simple way for tester to contribute

<Jean-Francois_Hector> https://src-bgsqvhqidk.now.sh/

JF: We talked about design about 2 things, about which would be the best way to do it.
... We talked about minimum requirement for testing, who tested it, how we could keep track of these informaiton.

<mck> Site listing open source test management systems:

<mck> http://www.opensourcetestmanagement.com/

Matt: I think there are probably 3-4 components of sturucture. 1.Test management system: Hold basi info of the testing. 2.Data model 3.Issue management:Using GitHub? 4.Reporting system:E.g. Use case discussion.
... Wtihin 8-10 weeks, I think we would have solid idea of few or one options suitable.

Michael: I'm curous that approach and how it would pan out. For issue 6, is it worth keep iterating this design?

Matt: Maybe not. What are some of yoru concerns for building on top of existing software vs somethign else?

Michael: General tradeoff of using existing software is they are designed for specific use case. If they are not fit for our testing need, so we might need to adjust ourselves for the tool.

JF: I agree with the idea of bringing someoneelse who have expertise. Perhaps one question would be what about using Michael's ineterface we already developed?

Matt: THat's a good example of what the system would look like.

Michael: Its lot broader than the work we've been discusssing so it requires modification. But we can obviously incorporate that.
... Current version doesn't track issue, and who've done the testing.

Matt: We might want to show our use cases for the testers.

Michael: In my project, I'm defining assertion at the feature level.
... Are we customizing assertion per SR level?

Matt: Not the assertion itself. I was envisioning SR-neutral level.

<michael_fairchild> A recent test that I put together for a11ysupport: https://a11ysupport.io/tests/tech__html__select

Develop assertion model for SR testing (Issue #5)

Matt: I think the conversation is about granurarity of assertion. All assertion shoudl be SR neutral.
... There might be some assertions that are not appropriate for given SR. e.g. augomatic mode switching for windows.
... When it gets down to specific features, we can potentially have one assertion ofr aria role/state/property. But in practice we won't test in that way.
... No.1 audience would be SR developers. So We need to present this to help them identify what the bugs are.
... 2 things to go: 1.Need to spend more time populating the spreadsheet. 2.When it comes to sharing these documents for SR developers, it should be generic enough to makae sense to them.

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)

Present: Matt_King jongund Yohta michael_fairchild
No ScribeNick specified.  Guessing ScribeNick: shimizuyohta
Inferring Scribes: 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: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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.)