Views
Quality/dataflow
From MeeGo wiki
(Difference between revisions)
(→Use case vs. Dataflow vs. Verification) |
(→Example of dataflow test cases) |
||
| Line 9: | Line 9: | ||
* On top of MeeGo API: “call QT bear management API connect with AP SSID to establish connection” | * On top of MeeGo API: “call QT bear management API connect with AP SSID to establish connection” | ||
* On top of Platform API: “call ConnMan d-bus API connect with AP SSID to establish connection” | * On top of Platform API: “call ConnMan d-bus API connect with AP SSID to establish connection” | ||
| + | |||
| + | [[File:api_demo.JPG]] | ||
== Illustrative example of the Dataflow diagram == | == Illustrative example of the Dataflow diagram == | ||
== Example list of Dataflow test cases (not full list) == | == Example list of Dataflow test cases (not full list) == | ||
Revision as of 07:19, 28 June 2011
Contents |
Dataflow definition
Dataflow is the flow of data to, from and within a device. Inputs are derived from system use cases and each core dataflow test case presents the basic instance of the use case in MeeGo core stack. The result of core dataflow could report the maturity level of MeeGo core os software and hardware integration on specific device.
Example of dataflow test cases
WLAN connect
- On top of UI: “open network applet, select AP SSID, click connect”
- On top of MeeGo API: “call QT bear management API connect with AP SSID to establish connection”
- On top of Platform API: “call ConnMan d-bus API connect with AP SSID to establish connection”
