Hi,
Full meeting log and meeting minutes:
http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-07-26-12.00.html
Meeting summary
---------------
* Current status (E-P, 12:00:12)
* QA ToDo list updated and tasks added (E-P, 12:00:28)
* Test coverage draft done,
https://wiki.merproject.org/wiki/Quality/Test_coverage (E-P,
12:01:08)
* Test execution howto
https://wiki.merproject.org/wiki/Quality/ExecuteTests (E-P,
12:01:32)
* OTS replacement (E-P, 12:17:08)
* features that make it different from ots (E-P, 12:17:28)
* transition cost based test distribution (e.g. don't reflash device
when not needed, send test to device that already has necessary
image flashed ) (E-P, 12:17:36)
* support for running non-packaged tests (E-P, 12:17:56)
* web ui for queue observation/control/access to logs/results /
workers maintenance info (E-P, 12:17:59)
* ability to restart workers or server (e.g. for upgrade) without
stopping tests (E-P, 12:18:03)
* usage of multiple devices in single testcase (E-P, 12:18:06)
* less interesting things (planned): pre/post device analysis, gradual
results submission (live progress monitoring), testcase modification
on-the-fly (for long-period-testing) (E-P, 12:18:11)
* LINK: http://wiki.meego.com/Quality/QA-tools/Test_packaging
(phaeron1, 12:39:10)
* LINK: http://wiki.meego.com/Quality/QA-tools/Test_package
(phaeron1, 12:39:54)
* ACTION: stskeeps to investigate if we can do rpm custom fields or
otherwise relay information out of band when building test package
(Stskeeps, 12:50:30)
* currently it is called as dister (E-P, 12:55:23)
* dister has 2 kinds of modules (E-P, 12:55:27)
* 1. test case providers - know how to split your request into Tasks
(minimal units of execution) (E-P, 12:55:30)
* 2. execution drivers - know how to execute Tasks on devices (vm,
hardware, robots, etc). (E-P, 12:55:34)
* task distribution is made regardless of provider & driver (E-P,
12:55:37)
* tasks know their requirements, inputs, and the name of driver (E-P,
12:55:42)
* defining test and environment requirements are under planning (E-P,
12:56:04)
Meeting ended at 12:57:56 UTC.
Action Items
------------
* stskeeps to investigate if we can do rpm custom fields or otherwise
relay information out of band when building test package
-E-P
On Wed, Jul 25, 2012 at 4:10 PM, Esa-Pekka Miettinen
<[email protected]> wrote:
> Hi,
>
> We will have the next Mer QA meeting tomorrow, Thursday 26th of July
> 2012 at 12 UTC in #mer-meeting.
>
> Agenda for the meeting is following:
>
> 1. Current status
> * The last meeting minutes:
> http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-07-19-12.00.html
>
> 2. OTS replacement
> * Current status and plans for the future
>
> If you would like to add anything to the agenda please let me know.
>
> -E-P
> Mer QA Technical Lead
