15:37:40 RRSAgent has joined #mwts 15:37:40 logging to http://www.w3.org/2009/01/27-mwts-irc 15:37:44 Zakim has joined #mwts 15:57:23 RRSAgent, make log public 15:57:23 Zakim, this will be TS 15:57:23 "TS" matches I18N_ITS IG()11:00AM, and MWI_TSWG()11:00AM, dom 15:57:23 Meeting: MWI Test Suites Working Group teleconf 15:57:33 Zakim, this will be TSWG 15:57:33 ok, dom; I see MWI_TSWG()11:00AM scheduled to start in 3 minutes 15:58:32 Agenda: http://lists.w3.org/Archives/Public/public-mwts/2009Jan/0020.html 15:58:37 Chair: Wilhelm 15:59:55 Carmelo has joined #mwts 16:00:09 MWI_TSWG()11:00AM has now started 16:00:11 +??P1 16:00:49 +??P54 16:00:50 -??P54 16:00:50 +??P54 16:01:12 +Carmelo 16:01:40 zakim, code? 16:02:00 the conference code is 8794 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), dom 16:02:10 dsilaev has joined #mwts 16:02:12 +Wilhelm 16:02:24 +??P9 16:02:32 zakim, who's on the call? 16:02:50 Carmelo is here 16:02:57 On the phone I see ??P1, ??P54, Carmelo, Wilhelm, ??P9 16:03:33 Topic: Widgets testing 16:03:39 zakim, ??P9 is dom 16:03:42 zakim, ??P1 is Kai 16:03:48 zakim, ??P54 is dmitri 16:04:00 ACTION: Kai to continue integrating his tests WTF [recorded in http://www.w3.org/2008/12/02-mwts-minutes.html#action02] [PENDING] 16:04:08 Kai: still pending; would be good to get help from Robert 16:04:15 Wilhelm: I'll make sure he follows up 16:04:27 +dom; got it 16:04:27 -> http://lists.w3.org/Archives/Public/public-mwts/2009Jan/0018.html request to review testability of spec 16:04:31 +Kai; got it 16:04:40 +dmitri; got it 16:05:14 dom: they're asking for review/help on testability of the spec 16:05:29 kai: spent quite a bit of time with Marcos working with him on the specs and tests 16:05:45 ... I think he's happy now - if a bit overwhelmed :) 16:06:29 wilhelm: any specific further action needed from us? 16:06:37 kai: nothing specific, just keep doing our work 16:06:43 Topic: Device independent testing guidelines 16:06:51 ACTION: Dmitri to review the DI guidelines [recorded in http://www.w3.org/2008/12/16-mwts-minutes.html#action04] [DONE] 16:06:59 -> http://www.w3.org/mid/496CBD09.8020704@sun.com Dmitri's comments 16:07:28 Dmitri: dom sent a reply to my comments, and asked for specific contributions 16:07:34 ... I'll work on it this week 16:07:58 ACTION: Dmitri to make a proposal on dividing guidelines per test components 16:08:12 ACTION: Dom to review the di guidelines [recorded in http://www.w3.org/2008/11/18-mwts-minutes.html#action09] [DONE] 16:08:44 -> http://lists.w3.org/Archives/Public/public-mwts/2009Jan/0021.html Dom's new version of guidelines 16:09:01 -> http://dev.w3.org/2008/dev-ind-testing/guidelines.html New version of the guidelines 16:09:09 ACTION: Wilhelm to review new version of guidelines 16:09:15 ACTION: Carmelo to review new version of guidelines 16:09:20 ACTION: Kai to review new version of guidelines 16:09:31 Topic: Memory Test 16:09:43 ACTION: Kai to implement binary search tree to determin limits of memory test [recorded in http://www.w3.org/2009/01/13-mwts-minutes.html#action06] [DONE] 16:09:56 -> http://www.w3.org/mid/b24851260901250841n3221c193p466cb30f6785ccb5@mail.gmail.com Kai's announcement of implementation 16:10:05 -> http://static.webvm.net/json Memory test 16:10:21 Wilhelm: how I should run it? How do I know if I'm getting the proper results? 16:10:38 Kai: it starts with the highest test; if that doesn't work, you go to lowest 16:10:49 ... and then you go to middle steps 16:11:11 q+ to ask what 'what doesn't work' mean? 16:11:23 ... one pb is that if you start too high, you may crash the browser 16:11:48 ... on my nokia device, I tried that, crashed the browser, and the memory wasn't cleared 16:12:14 ack dom 16:12:14 dom, you wanted to ask what 'what doesn't work' mean? 16:12:38 Kai: when it works, it gives you a message "server limit exceeded" or something like that 16:13:11 ... user agents with good memory capabilities can reach that 16:13:18 ... it's roughly for 2 Mo of data 16:13:51 Dom: maybe we could have something more user friendly than "server limit exceeded" :) ? 16:14:00 ... if we want to further advertise that test 16:14:15 Kai: could this be brought to another server to reduce the load on my server? 16:14:34 ACTION: Dom to check if we can host the memory test on a W3C server 16:14:53 ACTION: Kai to make success message in memory test more userfriendly 16:15:07 Kai: currently the generation of the data is kind of intensive 16:15:18 Dom: why is it generated on the fly? 16:15:26 Kai: it was the easiest way of doing it :) 16:15:43 ... I could probably be doing it more efficiently 16:15:57 ... but in any case, this is likely to create load on whatever server hosts it 16:16:15 ... code is written in shell, should be fairly easy to read 16:16:57 ... Apprently, IE Mobile can't go over 1MB 16:17:09 ACTION: Dom to run the memory test on his devices [recorded in http://www.w3.org/2009/01/06-mwts-minutes.html#action08] [PENDING] 16:17:18 ACTION: Wilhelm to run the memory test on his devices [recorded in http://www.w3.org/2009/01/06-mwts-minutes.html#action07] [PENDING] 16:17:24 Topic: Web Compatibility Test 16:17:42 ACTION: Kai to look into creating test cases for SSL and certificates support on mobile [recorded in http://www.w3.org/2009/01/13-mwts-minutes.html#action09] [PENDING] 16:18:00 Kai: I think I might have given up on this - it is really difficult to come up with something 16:18:28 ... I would really like to make sure user agents allow to see trusted roots 16:18:31 ACTION: Kai to look into creating test cases for SSL and certificates support on mobile [recorded in http://www.w3.org/2009/01/13-mwts-minutes.html#action09] [DROPPED] 16:18:36 RRSAgent, drop action 13 16:18:55 ACTION: Kai to push forward with finding a replacement for the inputmode test [recorded in http://www.w3.org/2008/12/16-mwts-minutes.html#action07] [PENDING] 16:18:59 Kai: no progress on my side 16:19:08 ACTION: WIhelm to look into replacement for inputmode test [recorded in http://www.w3.org/2009/01/06-mwts-minutes.html#action05] [PENDING] 16:19:15 Wilhelm: a couple of possible interested areas: 16:19:34 ... javascript timers - I'm writing a spec and tests around them 16:19:36 http://people.opera.com/wilhelmja/timers/tests/ 16:19:49 Kai: is there any problem with timers? 16:19:59 Wilhelm: sometimes they're inaccurate, sometimes they don't work 16:20:02 Notes: http://people.opera.com/wilhelmja/timers/data.html 16:21:00 Wilhelm: another idea would be MathML through CSS 16:21:12 ... not sure if that can be done with red/green square 16:21:28 ... I'm also going through the DOM specs to see if I can find something interesting there 16:21:38 Kai: I'll look in the timers stuff myself 16:21:52 Wilhelm: there is no spec for it yet 16:22:04 Kai: no spec from ECMAscript on this? 16:22:28 Wilhelm: nope; only ancient documentation from mozilla, and some stuff in html5 16:22:38 Kai: isn't MathML an XML-namespaced thing? 16:22:51 Wilhelm: it is, but the CSS profile for it is significantly simpler 16:23:17 Topic: Blog 16:23:42 -> http://www.w3.org/2005/MWI/Tests/blog/2009/01/19/what_s_measured_improves_1 What's measured improves, by Kai 16:23:50 Wilhelm: what should be our next post? 16:23:59 Kai: maybe talking about our search for a new test? 16:24:03 Wilhelm: sounds good 16:24:13 ACTION: Kai to prepare a blog post 16:25:05 Dom: Paul Nelson left a comment on the HTTPS test 16:25:19 ACTION: Wilhelm to follow up on the blog comment re HTTPS 16:25:31 Topic: Agreement on test suites with OMA 16:25:40 ACTION: Wilhem to send Opera's feedback on OMA test suites [recorded in http://www.w3.org/2008/11/18-mwts-minutes.html#action16] [PENDING] 16:25:52 ACTION: Dom to look back at OMA situation and report [recorded in http://www.w3.org/2008/11/18-mwts-minutes.html#action15] [PENDING] 16:25:58 Topic: Rechartering 16:26:24 Carmelo: will follow-up on NIST re-joining 16:26:47 Topic: Report from AWTA 2009 16:27:02 -> http://awta.wikispaces.com/AWTA+2009 AWTA 2009 16:27:14 Wilhelm: small but active conference, with 25 participants 16:27:28 ... around the Watir framework that can be used to automate browser testing 16:27:39 ... originally built for IE around COM components 16:27:50 ... can be used to make browsers do anything 16:28:01 ... various people are working on extending this to other browsers 16:28:10 ... we made a presentation on our Opera implementation 16:28:22 ... can be done on any opera device 16:28:30 ... it's made for being used over the wire 16:29:02 ... There was discussions on the different frameworks used 16:29:10 ... and how web applications testers did their testing 16:29:20 ... I think it's an important community to keep an eye on 16:29:44 ... cross-browsers support for this could permit automate testing for web standards conformance 16:30:07 dom: were there other browser vendors? 16:30:25 Wilhelm: nope, but someone has implemented it for Safari through Applescript 16:30:47 ... I think there is official support from the Chrome Team 16:30:58 Dom: any opportunity for getting other browsers to join that effort? 16:31:10 Wilhelm: no official support for IE, but it "just works" 16:31:38 ... the firewater implementation for firefox is not officially supported by Mozilla, but the extension mechanism allows to do it fairly simply 16:31:53 s/firewater/firewatir/ 16:32:38 dom: but is there any need to help there, or is just a matter of letting the community provide whatever is needed? 16:33:15 wilhelm: running code is mostly what's needed at this point 16:33:46 ... getting browser vendors to support this officially would be great, but isn't strictly required 16:33:58 kai: was there any talk about pocket IE? 16:34:05 Wilhelm: no, it wasn't 16:34:11 ... not sure what APIs they expose 16:34:20 Kai: I think it should be easy 16:35:47 Wilhelm: our implementations has 3 parts: the opera binary, to which you can communicate through a documented protocol, a proxy that connects to the binary, and tests scripts based 16:35:56 ... we're adding support for Watir in our tests scripts 16:36:08 -> http://wtr.rubyforge.org/ Automated testing that doesn’t hurt 16:36:26 http://dev.opera.com/articles/view/opera-dragonfly-architecture/ 16:37:00 Kai: support for Watir needs to be added in Opera binary? 16:37:25 Wilhelm: some can be added through javascript; some require new APIs in the binary, which we are adding 16:38:15 Topic: Next meeting 16:38:20 Next week (Feb 3rd) 16:38:42 -dmitri 16:38:44 dom: it's not such much Marcos was overwhelmed, it's more that Marcos is worried about the unstabiblity of the spec. Though i'm managing that. just need get people's expectations a little slower. 16:38:49 -Wilhelm 16:38:59 s/dom:/dom,/ 16:39:42 -Kai 16:39:44 -dom 16:39:45 MWI_TSWG()11:00AM has ended 16:39:47 Attendees were Carmelo, Wilhelm, dom, Kai, dmitri 16:39:51 RRSAgent, draft minutes 16:39:51 I have made the request to generate http://www.w3.org/2009/01/27-mwts-minutes.html dom 16:39:53 zakim, bye 16:39:53 Zakim has left #mwts 16:40:13 s/ ->/ ->/g 16:40:15 RRSAgent, draft minutes 16:40:15 I have made the request to generate http://www.w3.org/2009/01/27-mwts-minutes.html dom 16:41:32 wilhelm: is the opera protocol the same one used in opera mini <-> server communication ? 16:42:46 No. That's something completely differerent. The scope protocol is for sending commands to the browser and get something back. The Opera Mini servers transcode websites from HTML to OBML (Opera Binary Markup Language), which is a propertiary compressed format. 16:48:02 wilhelm: thank you for the clarification :) 16:48:53 We use scope for remote debugging with our Dragonfly tool, which is similiar to Firebug. 16:52:51 RRSAgent, bye 16:52:51 I see 19 open action items saved in http://www.w3.org/2009/01/27-mwts-actions.rdf : 16:52:51 ACTION: Kai to continue integrating his tests WTF [recorded in http://www.w3.org/2008/12/02-mwts-minutes.html#action02] [PENDING] [1] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-04-00 16:52:51 ACTION: Dmitri to review the DI guidelines [recorded in http://www.w3.org/2008/12/16-mwts-minutes.html#action04] [DONE] [2] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-06-51 16:52:51 ACTION: Dmitri to make a proposal on dividing guidelines per test components [3] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-07-58 16:52:51 ACTION: Dom to review the di guidelines [recorded in http://www.w3.org/2008/11/18-mwts-minutes.html#action09] [DONE] [4] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-08-12 16:52:51 ACTION: Wilhelm to review new version of guidelines [5] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-09-09 16:52:51 ACTION: Carmelo to review new version of guidelines [6] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-09-15 16:52:51 ACTION: Kai to review new version of guidelines [7] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-09-20 16:52:51 ACTION: Kai to implement binary search tree to determin limits of memory test [recorded in http://www.w3.org/2009/01/13-mwts-minutes.html#action06] [DONE] [8] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-09-43 16:52:51 ACTION: Dom to check if we can host the memory test on a W3C server [9] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-14-34 16:52:51 ACTION: Kai to make success message in memory test more userfriendly [10] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-14-53 16:52:51 ACTION: Dom to run the memory test on his devices [recorded in http://www.w3.org/2009/01/06-mwts-minutes.html#action08] [PENDING] [11] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-17-09 16:52:51 ACTION: Wilhelm to run the memory test on his devices [recorded in http://www.w3.org/2009/01/06-mwts-minutes.html#action07] [PENDING] [12] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-17-18 16:52:51 ACTION: Kai to look into creating test cases for SSL and certificates support on mobile [recorded in http://www.w3.org/2009/01/13-mwts-minutes.html#action09] [DROPPED] [14] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-18-31 16:52:51 ACTION: Kai to push forward with finding a replacement for the inputmode test [recorded in http://www.w3.org/2008/12/16-mwts-minutes.html#action07] [PENDING] [15] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-18-55 16:52:51 ACTION: WIhelm to look into replacement for inputmode test [recorded in http://www.w3.org/2009/01/06-mwts-minutes.html#action05] [PENDING] [16] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-19-08 16:52:51 ACTION: Kai to prepare a blog post [17] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-24-13 16:52:51 ACTION: Wilhelm to follow up on the blog comment re HTTPS [18] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-25-19 16:52:51 ACTION: Wilhem to send Opera's feedback on OMA test suites [recorded in http://www.w3.org/2008/11/18-mwts-minutes.html#action16] [PENDING] [19] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-25-40 16:52:51 ACTION: Dom to look back at OMA situation and report [recorded in http://www.w3.org/2008/11/18-mwts-minutes.html#action15] [PENDING] [20] 16:52:51 recorded in http://www.w3.org/2009/01/27-mwts-irc#T16-25-52