00:00:11 ... why don't we take a checkpoint at our next f2f and see where we are then? 00:00:36 s/SimonSapin/sstewart6 00:00:54 :) 00:01:16 http://lists.w3.org/Archives/Public/public-browser-tools-testing/ 00:01:26 Thanks wilhelm. Beat me to it 00:02:45 https://dvcs.w3.org/hg/webdriver/raw-file/default/webdriver-spec.html 00:03:06 https://dvcs.w3.org/hg/webdriver/ 00:07:00 [discussion about dealing with helping each other keep the group's work on schedule] 00:08:24 https://www.dropbox.com/s/m56rgbr1k04ms2v/2011-04-05%2021.20.04.jpg 00:08:35 ato: we should follow up quickly on code reviews 00:08:45 https://www.dropbox.com/s/y0sys1qwcr44afb/2011-04-05%2021.22.41.jpg 00:09:01 wilhelm: if we get everybody to each do some small part of the work 00:09:57 action: Wilhelm to regularly contact WG members to follow up on work 00:10:54 http://testthewebforward.org/ 00:11:04 https://code.google.com/p/selenium/source/browse/java/client/test/org/openqa/selenium/ 00:12:33 wilhelm: homework for tomorrow everybody should look at the tests in the open-source project, find some bit you like, and be ready to commit to working on that bit 00:14:56 JohnJansen: [describes the mechanism the CSS WG uses to determine which requirements in the spec have tests] 00:15:23 https://www.w3.org/wiki/WebDriver/2014-February-F2F#Day_Two 00:15:24 action: JohnJansen to investigate setting up a mechanism to sstewart6: https://www.w3.org/wiki/WebDriver/2014 00:16:10 action: JohnJansen to investigate setting up a mechanism to determine which requirements in the spec have tests 00:16:51 adjourned 00:16:57 until tomorrow 00:17:06 RRSAgent, make minutes 00:17:06 I have made the request to generate http://www.w3.org/2014/02/26-testing-minutes.html MikeSmith 00:20:32 jimevans has left #testing 00:22:04 sam has joined #testing 00:29:05 kennyluck has joined #testing 00:34:23 sstewart6 has joined #testing 01:19:29 RRSAgent, bye 01:19:29 I see 27 open action items saved in http://www.w3.org/2014/02/25-testing-actions.rdf : 01:19:29 ACTION: sstewart6 to talk to CSS WG about visibility detection [1] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T17-28-29 01:19:29 ACTION: Automate_ to speak to Tantek about his old action item on visibility and hit testing [2] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T17-29-01 01:19:29 ACTION: sstewart6 to add prefix to JSON URLs [3] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T17-42-45 01:19:29 ACTION: ato__ to switch to wptserve in webdriver test suite [4] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T18-01-15 01:19:29 ACTION: AutomatedTester to add a flag to take element screenshot without scrolling [5] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T18-43-54 01:19:29 ACTION: sstewart6 to define that cookies can only be set against domains that are currently loaded [6] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T18-46-13 01:19:29 ACTION: AutomatedTester to add whether it's a session cookie, a secure cookie [7] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T19-00-10 01:19:29 ACTION: AutomatedTester to link to the cookies RFC to describe the data format for expiry [8] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T19-00-50 01:19:29 ACTION: sstewart6 to describe how we send files across the wire [9] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T19-20-52 01:19:29 ACTION: sstewart6 to lowercase platform names [10] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T19-25-52 01:19:29 ACTION: sstewart6 to remove id location strategy [11] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T19-42-41 01:19:29 ACTION: sstewart6 to remove CSS selector capability (it's assumed) [12] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T19-42-59 01:19:29 ACTION: sstewart6 to add a note that you can use extension mechanisms to add location strategies [13] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T19-43-53 01:19:29 ACTION: ato to research root element behaviour in HTML and XML [14] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T20-07-30 01:19:29 ACTION: Luke to identify new endpoint for hooking switch to parent into [15] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T21-55-52 01:19:29 ACTION: Simon to define frame in section 6.1 [16] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T21-56-11 01:19:29 ACTION: David to review references to ensure they meet transition requirements [17] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T22-02-58 01:19:29 ACTION: John to send some spec language for window minimize [18] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T22-48-57 01:19:29 ACTION: Luke to port Seleniium async script test to spec testsuite [19] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T22-54-25 01:19:29 ACTION: Add definition for getElementText to the appropriate section of spec [20] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T23-02-18 01:19:29 ACTION: add language clarifying that drag and drop between frames in different domains should (must?) be supported [21] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T23-39-34 01:19:29 ACTION: Andreas TT to write some example tests for cases discussed at f2f, including handlers to add to wptserve [22] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T23-40-59 01:19:29 ACTION: Marc to lead work on separate minimal implementation of spec for inclusion in w-p-t repo [23] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T23-53-05 01:19:29 ACTION: wilhelm to work on making a small canonical set of tests that integrate with Marc's implementation [24] 01:19:29 recorded in http://www.w3.org/2014/02/25-testing-irc#T23-55-47 01:19:29 ACTION: Wilhelm to regularly contact WG members to follow up on work [25] 01:19:29 recorded in http://www.w3.org/2014/02/26-testing-irc#T00-09-57 01:19:29 ACTION: JohnJansen to investigate setting up a mechanism to sstewart6: https://www.w3.org/wiki/WebDriver/2014 [26] 01:19:29 recorded in http://www.w3.org/2014/02/26-testing-irc#T00-15-24 01:19:29 ACTION: JohnJansen to investigate setting up a mechanism to determine which requirements in the spec have tests [27] 01:19:29 recorded in http://www.w3.org/2014/02/26-testing-irc#T00-16-10 17:15:42 RRSAgent has joined #testing 17:15:42 logging to http://www.w3.org/2014/02/26-testing-irc 17:16:45 Topic: Browser testing & tools WG F2F, 26th of February 17:17:06 RRSAgent, draft minutes 17:17:06 I have made the request to generate http://www.w3.org/2014/02/26-testing-minutes.html wilhelm 17:17:32 jgriffin has joined #testing 17:17:40 gitbot has joined #testing 17:17:40 [13web-platform-tests] 15lukeis opened pull request #699: adding ability to configure alternate browsers (06master...06master) 02https://github.com/w3c/web-platform-tests/pull/699 17:17:40 gitbot has left #testing 17:17:48 lukeis has joined #testing 17:18:17 lukeis has joined #testing 17:18:17 Meeting: Browser testing & tools WG F2F, 26th of February 17:18:25 RRSAgent, draft minutes 17:18:25 I have made the request to generate http://www.w3.org/2014/02/26-testing-minutes.html wilhelm 17:19:00 first PR of the day! ;) https://github.com/w3c/web-platform-tests/pull/699 17:20:38 lmclister has joined #testing 17:22:00 jimevans has joined #testing 17:22:38 rhauck has joined #testing 17:23:21 rhauck has joined #testing 17:24:22 JohnJanse has joined #testing 17:24:52 JohnJanse has joined #testing 17:25:34 JohnJansen has joined #testing 17:25:59 rhauck1 has joined #testing 17:26:20 is this thing on? 17:26:49 seva has joined #testing 17:27:18 John, yes 17:31:24 sstewart6 has joined #testing 17:34:06 dannin has joined #testing 17:36:10 http://www.youtube.com/watch?v=qu9MptWyCB8 17:36:23 For some context about references to "fork handles" 17:37:13 sam has joined #testing 17:38:39 ShuotaoGao has joined #TESTING 17:38:51 rhauck has joined #testing 17:40:23 rhauck2 has joined #testing 17:49:12 Everyone reading 17:49:14 ready 17:49:15 even 17:49:18 ? 17:49:40 MarcFisher has joined #testing 17:49:44 Scribe: lukeis 17:49:56 Present+ Wilhelm 17:49:58 present+ JohnJansen 17:49:59 Present+ mdas 17:49:59 Present+ SimonStewart 17:50:00 Present+ jimevans 17:50:03 Present+ samuong 17:50:04 Present+ DaleAnnin 17:50:08 Present+ ShuotaoGao 17:50:08 Present+ LukeInman-Semerau 17:50:09 Present+ sevalo 17:50:12 Present+ DavidBurns 17:52:18 jleyba has joined #testing 17:52:32 sstewart6: the handle that was auto assigned to me 17:52:36 wilhelm: chairing 17:52:49 chair: wilhelm 17:52:57 https://www.w3.org/wiki/WebDriver/2014-February-F2F 17:52:58 Present+ ato 17:53:04 agenda: https://www.w3.org/wiki/WebDriver/2014-February-F2F 17:53:15 topic: end point uri for batching actions 17:53:48 AutomatedTester: yesterday landed user interactions part of the spec, one thing missing was how to send across the wire 17:54:24 AutomatedTester: user interactions going to be sending it across as one atomic action 17:54:30 I'm going to suggest "/session/{sessionId}/actions 17:54:32 " 17:54:43 gitbot has joined #testing 17:54:43 [13web-platform-tests] 15malini opened pull request #700: add tests for getElementAttribute (06master...06getElementAttribute) 02https://github.com/w3c/web-platform-tests/pull/700 17:54:43 gitbot has left #testing 17:54:47 AutomatedTester: [describes various api end points] 17:55:09 sstewart6: should we discuss touch actions / multi actions, do we know what they are? 17:55:16 some don't 17:55:17 https://dvcs.w3.org/hg/webdriver/raw-file/default/webdriver-spec.html#user-input 17:55:35 zcorpan has joined #testing 17:55:58 AutomatedTester: mouse / keyboard / touch (now with mobile) 17:57:05 AutomatedTester: [explains how current Actions / Touch actions work with single action being independent wire call] 17:57:32 AutomatedTester: [descibes 'multi-touch'] 17:58:48 seva: the multiple finger actions already in the project? 17:58:53 AutomatedTester / sstewart6: no 17:59:05 seva: batching actions in either? 17:59:08 AutomatedTester: no 17:59:50 sstewart6: everyone in agreement that batching actions is a good idea, waiting on spec definition 18:00:15 sstewart6: section 14.2.1 18:00:42 ACTION: keyboard actions AutomatedTester 18:01:31 jleyba: second bullet point [reads] 18:01:40 sstewart6: we should probably remove the word 'not' 18:02:35 AutomatedTester: discussing browser pauses 18:02:44 s/pauses/parses 18:02:52 s/parses/parsers 18:02:54 We should probably have some actions on the things raised by jleyba. 18:03:19 sstewart6: 14.2.1, should probably be efficient 18:04:24 rhauck has joined #testing 18:04:27 mdas_: it will perform all the actions? 18:04:41 sstewart6: [handwaving / explaining] 18:05:10 action: edit 14.1 to clarify the HTML4 'disabled' statements AutomatedTester 18:05:49 sstewart6: if you are about to run out of memory on a device and the actions will cause an out of memory with the commands, there's no way around that in the spec 18:06:28 sstewart6: we would use MUST if there was a level between MUST and SHOULD 18:06:43 abarsto has joined #testing 18:08:38 ACTION: change enum to match rest of spec 14.2.1.1 18:08:38 14.2.1.1 18:08:58 rhauck1 has joined #testing 18:10:36 discussing mouse button naming 'LEFT' 'RIGHT' 18:11:21 sstewart6: 'LEFT' equates to normal usage when pressing 'LEFT' button on the mouse 18:11:29 abarsto1 has joined #testing 18:11:42 seva: problem when it comes to expanding support 18:12:46 ato: if javascript decides there's other mouse events we'll need to expand also 18:13:06 sstewart6: if the dom spec changes we need to change also 18:13:24 ACTION: put reference to the dom spec version we are using 18:13:31 wilhelm: which one?? 18:14:17 ACTION: double click should take a button 18:14:58 RRSAgent, make minutes 18:14:58 I have made the request to generate http://www.w3.org/2014/02/26-testing-minutes.html MikeSmith 18:15:06 Present+ MikeSmith 18:15:07 ato: what about triple / quadruple click? 18:16:16 sstewart6: to do double click: down/up, down/up to do two clicks down/up, pause, down/up 18:16:52 sstewart6: we have a constant for pause sent across the wire to handle differences in OSes 18:17:29 sstewart6: we don't have a pause action 18:17:52 seva: shortest possible pause? 18:18:15 ato / sstewart6: we want it to be on the remote side 18:18:43 Ms2ger has joined #testing 18:19:07 jleyba: 0 based timeout in javascript isn't actually 0 18:19:37 sstewart6: i'm not worried about the click, i'm worried about the double click, don't know what the pause is because it's known only by the operating system 18:20:22 sstewart6: probably a registry setting in windows 18:20:42 JohnJansen: yes, i'm worried about accessibility inserting the pausing 18:21:03 mdas_: [gives explanation to alleviate concerns] 18:21:19 i/SimonSapin/scribe: MikeSmith 18:21:22 RRSAgent, make minutes 18:21:22 I have made the request to generate http://www.w3.org/2014/02/26-testing-minutes.html MikeSmith 18:21:38 [down, up, down, up] 18:21:48 [down, up, sys-pause, down, up] 18:21:49 scott_gonzalez has joined #testing 18:21:58 sstewart6: first would be a double click, second two separate clicks 18:22:10 i/take a checkpoint/scribe: MikeSmith 18:22:14 RRSAgent, make minutes 18:22:14 I have made the request to generate http://www.w3.org/2014/02/26-testing-minutes.html MikeSmith 18:22:47 mdas_: is it universal across browsers? 18:23:39 https://github.com/operasoftware/operadriver/blob/master/src/com/opera/core/systems/scope/stp/services/ScopeExec.java#L116 18:23:47 ato: did some testing, finding a 'safe' number to separate clicks, 640ms 18:25:22 ACTION: so one proposal is to remove click and double click from mouse, use down/up - sstewart6 18:27:22 ato: [talks about using event queue] 18:28:12 ACTION: add description on how to process the batch - AutomatedTester 18:29:47 lukeis: asks about 'standard' common actions 18:29:59 sstewart6: we'll add that to the non-normative section on batching 18:30:41 sstewart6: i think we don't need perform on the action 18:32:22 glenn has joined #testing 18:32:35 ACTION: remove perform from all X-action 18:33:05 14.2.1.1.1 18:33:32 sstewart6: there are references to 'any' button, but it's specified 18:35:19 ACTION: clean up the prose in 14.2.1.1.1 (well, all the way through) regarding 'any' and require the button argument, not optional 18:36:02 sstewart6: if buttonUp is done when no button is down what do we do? 18:36:07 mdas_: we throw an error 18:36:47 jimevans: we absolutely need to keep track of the buttons pressed 18:37:16 ato: had to add the extra behavior of keeping track of buttons to keep in line with selenium 18:37:34 sstewart6: we need to define the behavior, throwing makes sense 18:38:17 ato: what's the error code? 18:38:26 sstewart6: we could have illegal argument 18:40:02 ACTION: moveTo specify the initial start point, should be 0,0 of current top level browser context 18:40:27 ACTION: add exception information in the mouse action section if we have incomplete actions 18:44:00 ACTION: to specify that the mouse's current cursor location is relative to the current viewport and not to the document 18:44:30 sstewart6: and with that i'm out of comments for mouse actions 18:44:30 ACTION: update the table in moveTo to match the prose above regarding no webelement passed in AutomatedTester 18:45:00 ato: explain how the optional arguments work? 18:46:10 MarcFisher has joined #testing 18:46:23 ACTION: moveTo gets mandatory WebElement optional x/y. moveToOffset gets mandatory x/y 18:47:30 seva: implementations must support both batching and non? 18:47:34 s/moveToOffset/moveByOffSet 18:48:05 sstewart6: the interface will remove the un-batched, and a 'single' item can be sent in a batch request 18:48:13 dannin: what about middle button scrolling? 18:48:43 sstewart6: we need scroll wheel added to the spec 18:49:05 JohnJansen: [explains middle wheel scrolling] 18:49:47 ACTION: JohnJansen to find out what events get fired with middle wheel scrolling 18:50:53 sstewart6: enough of this madness 18:51:24 ato: asks about send keys / releasing implicitly 18:51:39 sstewart6: 14.3.3 18:53:16 sstewart6: Actions(SHIFT key); element.send_keys("a"); do you expect "A" or "a" 18:53:33 sstewart6: element.send_keys is do as I say, so it should be 'a' 18:54:34 ACTION: element.send_keys needs to talk about implicitly unsetting the modifier keys 18:55:58 sstewart6: offers lukeis advice 18:56:21 zcorpan has joined #testing 18:57:09 ACTION: we need to explicitly clarify the difference between batches with modifier keys then using element.send_keys and then using the actions again 18:57:33 14.2.1.2 18:57:59 sstewart6: why is wait on touch? 18:58:02 zcorpan has joined #testing 18:58:30 ACTION: wait should be moved to 'pause' action 18:58:59 RRSAgent, make minutes 18:58:59 I have made the request to generate http://www.w3.org/2014/02/26-testing-minutes.html MikeSmith 19:00:07 ACTION: tap and longpress to be removed 19:02:25 sstewart6 / AutomatedTester: discussing how we expose this to client bindings api 19:03:38 sstewart6 / mdas_: discuss cancel 19:03:51 ACTION: clarify definition of cancel - mdas 19:05:31 craigdh has joined #TESTING 19:06:49 ACTION: moveTo needs same replacement in 14.2.1.2 as 14.2.1 19:07:39 ACTION: be consistent with usage of 'Gesture' and 'Action' and we should not use 'gesture' 19:11:32 JohnJansen: what about trying to test that an element isn't currently in the viewport (without calling scrolling into view) 19:11:49 sstewart6: there's javascript that can be called to determine this 19:12:37 JohnJansen: it would be nice to know if the element had to be scrolled into view 19:14:28 ACTION: MUST scrollIntoView for touch events 'everywhere' 19:14:44 break for 15 19:15:17 scott_gonzalez has joined #testing 19:20:20 Automate_ has joined #testing 19:28:13 jgraham: hey, https://critic.hoppipolla.co.uk/r/890 is not updating after there was a |push -f| and then that was unrolled and repushed. Is there something that you can do? 19:31:53 AutomatedTester: I tried to do what I can do and then it gave an error that I have seen before but don't understand 19:32:38 Invalid history rewrite: No commit on the rebased branch references 19:32:40 remote: the same tree as the old head of the branch. 19:33:05 ahh 19:33:18 should I suggest killing the PR and redoing it? 19:33:30 jgraham: ^ 19:33:32 seva has joined #testing 19:33:38 Yeah, unless you are happy to just use github for this one 19:33:49 gitbot has joined #testing 19:33:49 [13web-platform-tests] 15lukeis closed pull request #699: adding ability to configure alternate browsers (06master...06master) 02https://github.com/w3c/web-platform-tests/pull/699 19:33:49 gitbot has left #testing 19:34:05 gitbot has joined #testing 19:34:05 [13web-platform-tests] 15lukeis reopened pull request #699: adding ability to configure alternate browsers (06master...06master) 02https://github.com/w3c/web-platform-tests/pull/699 19:34:05 gitbot has left #testing 19:34:22 sstewart6: ok guys and gals 19:34:44 jleyba has joined #testing 19:35:12 sstewart6: just finished 14.2.1.2.x … moving down 14.2.2 multi actions 19:37:41 scott_gonzalez has joined #testing 19:38:20 dannin: swipe down from edge of screen in BB can fire swipeDown event 19:39:12 ACTION: should create IDL for Action and extend all the way down 19:42:25 ACTION: svg for 'perform' diagram - mdas 19:45:49 s/multiaction/parallelaction 19:45:55 jobs 19:45:56 pwd 19:46:01 oofs 19:46:18 s/jobs// 19:46:22 kill -9 1 19:46:22 s/pwd/ 19:49:03 ACTION: rename multi-action to parallel-action 19:50:19 sstewart6: done with 14.2 19:50:51 sstewart6: to discuss end point uri for batches 19:50:56 Suggestion /session/{sessionId}/actions 19:52:55 ACTION: define batch uri to be /session/{sessionId}/actions and name to be 'perform actions' 19:53:32 sstewart6: json payload… an array of array of objects? (for parallel) 19:53:48 Straw man: [{down: {x: 30, y:30)], [] 19:54:44 [[down]], [[]]] 19:55:46 sstewart6: action: map containing name & parameters of that action 19:55:52 {name: 'touchDown', x: 30, y: 40} 19:56:58 example: [[{action}]] 19:57:56 jimevans has left #testing 19:58:02 [ [ {action1}, {action2}], [{action1p}, {actions2p}] ] 19:58:02 jimevans has joined #testing 19:58:46 zcorpan has joined #testing 19:59:15 rhauck has joined #testing 19:59:24 [ [ {tap}, {tap}, {click} ], [ {pause}, {pause}, {down}] ] 20:02:41 AutomatedTester: pause with no wait period is like a NoOp 20:03:53 in example above, what gets executed are (tap / pause) then (tap / pause) then (click / down) 20:04:54 AutomatedTester: the 'tick' is the longest action, a 'tick' is a grouping of actions run in parallel 20:06:06 seva: I'm happy :thumbs up: 20:08:58 ACTION: add the explanation of the json payload for batches - mdas 20:09:19 wilhelm: are ticks recursive? 20:09:21 sstewart6: no 20:10:03 break for lunch! 20:10:31 Ms2ger has joined #testing 20:27:59 sstewart6 has joined #testing 20:33:38 glenn has joined #testing 20:34:20 jleyba has joined #testing 20:34:40 abarsto has joined #testing 20:46:52 rhauck has joined #testing 20:52:36 sstewart6_ has joined #testing 20:54:40 glenn has joined #testing 20:56:23 jleyba: www.w3.org/2014/02/25-testing-minutes.html 20:58:19 Automate_ has joined #testing 20:59:29 zcorpan has joined #testing 21:00:27 scribe: ato 21:01:31 topic: Firing Touch Events 21:02:05 http://www.w3.org/2014/02/25-testing-minutes.html 21:02:41 Automate_: At the moment we're firing touch events because the pointer events spec isn't done yet. 21:02:44 They have a different ordering. 21:02:59 Is this something we should care about now? 21:03:04 mdas: Why do we have to specify this? 21:03:20 Automate_: It relates to the arguments being passed in. 21:03:31 wilhelm: Are we future proof with what we have now? 21:03:54 Automate_: At the moment it's quite fluffy, for a reason. But if we wanted to describe the ordering of a press, we might do. 21:04:39 wilhelm: I'm not familiar with the spec here. But my gut reaction is to push it to level 2, but to make sure we don't have to change what we have now in a year's time. 21:04:52 Automate_: I'd be fine with that. But I was worried about the people who are doing implementations now. 21:05:00 Because we could keep level 1 non specific. 21:05:16 Basically not specify any event specification. 21:05:25 I expect someone to raise a bug about it. 21:05:49 Are we all happy to leave it at that? 21:06:00 Sounds good. 21:06:15 wilhelm: Following up on homework from yesterday, and conformance spec suite work. 21:06:23 Are there any technical issues we should discuss before we begin? 21:06:28 Then I suggest we move to homework. 21:07:08 So we disucssed yesterday that to make sure we make progress on the test suite from now on, is that everyone pick a tiny area to do write some tests on. 21:07:13 Let's give it ten minutes. 21:07:19 Look in the spec or in the open source test suite. 21:07:27 And pick something interesting that you'd like to work on. 21:07:36 It can be two tests, it can be really small. It doesn't matter. 21:07:40 Just pick something. 21:07:45 The point is to get the wheels moving. 21:07:45 Bagsy window switching 21:08:08 Action: sstewart6 to look at window switching tests 21:08:27 Action: mdas to look at modal 21:08:28 Pick something, add an action, and we'll get to work. 21:08:33 ACTION: AutomatedTester to look at screenshots 21:08:35 ACTION: lukeis to look at frame switching tests 21:09:12 Note: I have a small PR for getElementState as well 21:09:36 lukeis: So are we happy with the flat file directory structure, or do we want nested folders? 21:09:46 ACTION: seva: look at adding conformance tests equivalent to those in org/openqa/selenium/PageLoadingTest.java 21:09:50 sstewart6: I'm happy with it. Doesn't like nested folders. 21:10:10 I'm weary of ordering. 21:10:33 ato: We did that with the spec. Bad mistake. 21:10:40 lukeis: Yes, we also had that with the Selenium documentation. 21:10:48 seva: Is that a problem? Can we remove the numbers? 21:11:03 ACTION: Wilhelm to write example tests for how other WGs should make WebDriver tests 21:11:10 sstewart6: It's a bad idea to reflect those numbers in the text. 21:11:47 lukeis: We can use a list in the Makefile. 21:12:02 ato: Yes. I refactored the Makefile to make that possible. 21:12:04 We should do that. 21:13:33 ACTION: jleyba to look at executeScript and executeAsyncScript tests 21:15:26 ACTION: jimevans to add conformance tests equivalent to those in org/openqa/selenium/ClearTest.java and org/openqa/selenium/ElementSelectingTest.java 21:15:45 This is the test repo tests should go into: https://github.com/w3c/web-platform-tests 21:16:19 Documentation for how to push things up there: http://testthewebforward.org/docs/ 21:16:36 ACTION: look at cookie related tests 21:19:08 AutomatedTester has joined #testing 21:19:42 rhauck has joined #testing 21:22:12 Automate_ has joined #testing 21:24:10