Meego Wiki
Views

Quality/QA-tools/MCTS test automation design/proof-of-concept-planning

From MeeGo wiki
< Quality | QA-tools | MCTS test automation design
Revision as of 14:01, 31 December 2010 by Asinnela (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
  • OpenAMQ to be used for Messaging Routing
    • Has C/C++ client API
  • Generic API provided for communicating with OpenAMQ client API
    • needs to be able to install both host and device
  • Proof-of-Concept
    • Reboot test case between two DUTs (N900)
    • External device would be HAT or older switchbox
step 1
Reboot DUT2 (command defined in test plan XML)
Message sent from testrunner-lite and routed to device API
Device API reboots device and and waits for desktop-ready -> event sent
step 2
Ping between DUT1 and DUT2
  • TODO
    • Check how parameters could be exchanged with AMQP
      • Does AMQP itself provide this?
      • Use JSON for example.
Retrieved from "http://wiki.meego.com/Quality/QA-tools/MCTS_test_automation_design/proof-of-concept-planning"
Personal tools