<inserted> scribenick: kaz

paul: Peter posted an issue on GitHub: https://github.com/w3c/automotive/issues/75

peter: had an action to put on testing
... goes through the issue description
... ex 1: ECMAScript bindings
... ex 2: Test the Web Forward

dave: any other W3C groups using this?

peter: don't know actually
... TTWF is a completely open group

<inserted> scribenick: ted

kaz: this was an open project run by adobe and others
... two years ago they asked w3c to take it over and we merged with our work

ted: if you're curious who else is using it besides w3c we can ask
... i don't know anyone offhand

kaz: i can ask mike for help in getting us setup in this system

peter: the join process is pretty spelled out
... the way you work with it is to fork and clone, then submit back your api

<kaz> fyi, the slides on W3C Web Platform Testing: https://docs.google.com/presentation/d/1IKpt626qpPnMpiFP9kbkTZaQPj9LST6Awa8d9zK7WCU/edit#slide=id.g4645dac6e_023

[on the github md page it lists whatwg as another user]

<kaz> https://docs.google.com/presentation/d/1IKpt626qpPnMpiFP9kbkTZaQPj9LST6Awa8d9zK7WCU/edit#slide=id.g4645dac6e_023

http://w3c-test.org/ is maintained by mike smith, philippe le hegaret, denis ah-kang and formerly robin berjon with some assistance from w3c systeam

<kaz> test runner server: http://w3c-test.org/tools/runner/index.html

<inserted> scribenick: kaz

kaz: Web&TV guys are trying to test TV runtimes
... so we could ask them as well for help
... also for test environment, we need some kind of emulator which provides car data instead of an actual car
... if we can use an IVI on an actual car, that's great
... but some of the developers need an emulator

peter: have some mechanism but applied to our customers (=car manufacturers)

dave: the idea is just emulating the data
... how realistic data we need?
... we might need only some edge cases

kaz: would agree

dave: e.g., provide the biggest/smallest data

paul: simple mechanism which provides CAN data?

dave: yes. for unit testing
... passing the test means being able to process the mocked data

paul: got it
... so what's the next step?

<inserted> scribenick: ted

kaz: during the previous call urata-san said he interested but busy
... they are working on an emulator that might be useful. also i will ask mike smith and TV guys for assistance in getting started

<inserted> scribenick: kaz

paul: what about refactoring the access methods?

-> https://github.com/w3c/automotive/issues/72 refactoring access method issue

ted: reviewing it
... talked with the domain lead of web api (plh)
... maybe might want to reconsider how to handle the time
... T0 for battery status, battery temp., etc.
... the maker may use HTML ids
... would follow email discussions

<ted> plh concerns with refactoring events along the lines of tobie's suggestion as a more contemporary way web apis are being created

<ted> follow that convention will make it easier for web developers to code against our api

paul: update for issue 72 with some thought

peter: will continue to look through Test the Web Forward

peter: started implementation already
... need to follow the original spec
... can't tell which would be better, the original style or the new style suggested during TPAC

kaz: we should start with a small set of APIs for testing
... esp. those which are surely available with the cheapest cars

paul: can provide a list of features
... can take an action for that

<scribe> ACTION: paul to provide a list of features which are surely available any kind of cars [recorded in http://www.w3.org/2015/12/10-auto-minutes.html#action01]

<trackbot> Created ACTION-11 - Provide a list of features which are surely available any kind of cars [on Paul Boyes - due 2015-12-17].

peter: also would see the guys work for Test the Web Forward
... getting a list of limited features for testing is good
... would have an ideal set of testing

<inserted> scribenick: ted

dave: why are they not using tools like jasmine instead?

paul: we use jasmine here. can it be as maintained though if we use it instead of test the web forward system
... i know there are other frameworks as well

dave: curious what adam (jlr) might use

adam: we would use any reasonable test tool

[kaz, when you talk to mike please ask him why not jasmine? was it underdeveloped then or does it continue to have a shortfall for testing web apis]

<kaz> ACTION: kaz to talk with Mike Smith about W3C Web Platform Testing and Jasmine [recorded in http://www.w3.org/2015/12/10-auto-minutes.html#action02]

<trackbot> Created ACTION-12 - Talk with mike smith about w3c web platform testing and jasmine [on Kazuyuki Ashimura - due 2015-12-17].

<inserted> scribenick: kaz

kaz: one quick note that the Test the Web Forward GitHub repo is exactly the one for the W3C Web Platform Testing
... we can use the test runner site if we add our tests to the repo

<scribe> ACTION: kaz to create a doodle poll to gather people's availability [recorded in http://www.w3.org/2015/12/10-auto-minutes.html#action03]

<trackbot> Created ACTION-13 - Create a doodle poll to gather people's availability [on Kazuyuki Ashimura - due 2015-12-17].

[ adjourned ]