Agenda
- Architecture design walkthrough (Riku)
- Proof-of-Concept Demo (Sami)
- Event-based communication using Apache Qpid
- Sending/ receiving events from testrunner-lite and test binary
- Lunch
- Implementation kick-off (All)
- Contributions to work from Tools/ Test development
- Priorities
- B.M.O features
- etc…
Minutes
Present: Parties for MeeGo QA Tools, MCTS/BLTS development, OSMW testing
- Status
- Draft version of C-wrapper for the subset of Messaging API
- Sequential event handling possible from testrunner-lite
- Event sending/ receiving possible from MeeGo DUT and control host
- Draft RPM-packaging exits for QPid
- Priorities from test development
- Priority 1: Automate phone test cases
- Target is to first to automate MO phone call between DUT and network analyzer
- Manual Verification Mode
- Suggested to use testrunner(-ui) to handle user interaction
- Decided to come back to this later as we may get get better ideas, when development kicks-off
- Parallel execution
- Agreed to describe it in a single tests.xml
- Details left open still. To be discussed later how to implement this
- Other
- Only simple event handling should not be in test plan XML. Just a basic request-response
- More complex handling should be in test binary
- test development to define guidelines "what is allowed to do and where"
- Actions
- Finalize testrunner-lite implementation from the event sending/receiving part (Sami/ Sampo & co)
- Finalize libqpidc (documentation, sub-set of features from C++ API) (Sami)
- Message sequences to control analyzer (Riku)
- Events for the analyzer to be defined with BLTS team.
- QPid, JSON library etc. packaging/integration to MeeGo (Joonas)
- Test-definition schema to support events?