Hello all, My two cents to this discussion:
We have been working with OF-HAT concept for quite some time now. One of the main goals for this activity is to get rid of currently proprietary USB Switch boxes and make this available for community members. USB and Power switching is needed for automatic flashing of handheld devices. As addition to this to get verification data from different sensors. One of the planned sensors (we have a prototype available) is Current Consumption sensor. With this you can measure current consumed by DUT with adequate level in order to evaluate SW change effects to current consumption. This is not mentioned for very accurate product specific measurements but instead for fast feedback to developers and for QA for functional testing. OF-HAT will be supported by OTS. What comes to contributing to MCTS it goes as follows: You are free to contribute to MCTS test assets providing new test cases, test components, documentation and so forth. In order to do so please take your own clone of current source code from http://gitorious.org/qatools/mcts. When you have new test cases available you can create commit. This will be reviewed by test assets maintainers listed at: http://wiki.meego.com/Quality/TestSuite/MCTS. If no objections your test assets will be merged to master. MeeGo common contribution guidelines are available at: http://meego.com/about/contribution-guidelines It is highly recommended to follow MCTS development guidelines at: http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Development_Guideline when developing test assets. We are currently working with more detailed contribution guidelines. In this specific case you are kind of creating test cases from the scratch and you should be considered as test asset maintainer. For garage, I don't know. Nevertheless it sounds a good idea. Br, Toropainen >-----Original Message----- >From: [email protected] [mailto:meego-qa- >[email protected]] On Behalf Of Tahvanainen Jari (Nokia- >MS/Helsinki) >Sent: 30. marraskuuta 2010 13:21 >To: Vatula Veli-Pekka (Nokia-MS/Tampere); [email protected]; >[email protected]; Rantalainen Niko.M (Nokia-MS/Tampere); Koski Petri >(Nokia-MS/Tampere) >Cc: [email protected] >Subject: Re: [Meego-qa] Proposal: Automatic power consumption testing > >Hi, > >+1 for this kind of tests executed daily. > >Could we make this as an "example run for a process"? > >Try to package tests (script) according instructions - >http://wiki.meego.com/Quality/QA-tools/Test_packaging. If something does >not work file a bug towards qa-tools. > >Niko, Petri: >... is there instructions somewhere how one can deliver/suggest test >asset to be included in mcts or handset-ux-tests ? >... is there going to be garage for Community test asset somewhere? I >suppose everything is not going to be part of official suites... > >Then execution is another thing ... and Niko and Petri should be able to >give clearance on that too. Surely OTS shall give possibility for >whoever to execute these kind of tests on certain hardware (e.g. on >N900) - but this is not totally public yet. > >Br, Jari > >-----Original Message----- >From: [email protected] [mailto:meego-qa- >[email protected]] On Behalf Of Vatula Veli-Pekka (Nokia- >MS/Tampere) >Sent: 30 November 2010 12:52 >To: [email protected]; [email protected] >Cc: [email protected] >Subject: Re: [Meego-qa] Proposal: Automatic power consumption testing > >I understand the benefit clearly... >So, you would like to have that for N900 in 1.2 Core. > >What kind of scripts you are having for this? > >V-PV > >-----Original Message----- >From: [email protected] [mailto:meego-qa- >[email protected]] On Behalf Of ext Sivan Greenberg >Sent: 30. marraskuuta 2010 12:13 >To: Carsten Munk >Cc: [email protected] >Subject: Re: [Meego-qa] Proposal: Automatic power consumption testing > >On Tue, Nov 30, 2010 at 11:21 AM, Carsten Munk <[email protected]> >wrote: > >> We concluded that to do this work properly, we need objective power >> consumption measurements and we have a script that using the battery >> meter can tell us roughly how many mA our power consumption is. >> >> So, here's the proposal: along with automatic testing, could it be >> possible to generate power consumption data of those testcases? >> >> I guess the same kind of framework would be useful on many other >> devices as power management is important for mobile devices in general >> :) And a power consumption hardware adaptation interface could be >> useful in other circumstances like battery meter. > >It would also enable us to objectively test community patches / power >management proposals. I know there are some already floating around >from Maemo waiting to be tested. > >> >> What's your thoughts? >++1 > >-Sivan >_______________________________________________ >MeeGo-qa mailing list >[email protected] >http://lists.meego.com/listinfo/meego-qa >_______________________________________________ >MeeGo-qa mailing list >[email protected] >http://lists.meego.com/listinfo/meego-qa >_______________________________________________ >MeeGo-qa mailing list >[email protected] >http://lists.meego.com/listinfo/meego-qa _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
