MeeGo Core Test Suite Current State and future workshop
MeeGo Core Test Suite (MCTS)  is set of test components intended for verification of MeeGo Core OS according to test plan  covering functional and non-functional (efficiency and reliability) aspects . MCTS is actively used by MeeGo Core OS QA. Currently MCTS offers more than 2000 test cases for various components including component level test cases and system level, E2E type test cases.
Typical characteristics for these component test cases are that they verify specific component or library with extensive set of parameters. Often they are missing E2E approach where entire stack is exercised. Test cases may not necessarily leave from component under test.
Typical characteristics for these system test cases are that they are based on use cases or user stories and often testing entire stack from top most interfaces provided by MeeGo Core OS Middleware and exercises HW peripheral beneath SW stack. These types of test cases are the most efficient ones for measuring and providing visibility to maturity of MeeGo Core OS.
Currently we have had contributions to MCTS from different sources and there are lots of variations in methods how test cases are created, test case quality and how test cases are documented. Also there are overlapping test cases e.g. currently BlueZ test cases can be found from three different test components.
For the future of MCTS I see following as key points.
Target of this activity is that MeeGo Developers can trust and rely on MCTS results with any hardware
As addition to these I see one more quite comprehensive element and it is freedom of test developers to choose language they want Python, Perl, C++, and so forth). In order to make usage of MCTS easy for anyone it is important to unify the ways test cases are defined, documented and so forth.
 MeeGo Core Test Suite - MCTS - http://gitorious.org/qa-tools/mcts
 MeeGo 1.2 Core OS Test Plan - http://wiki.meego.com/Quality/TestPlan/MeeGo_Core_Test_Plan
 Test Areas describing quality characteristics - http://wiki.meego.com/Quality/TestAreas
 Test definition - http://wiki.meego.com/Test_Packaging/Test_Plan
 MCTS Development Guideline - http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Development_Guideline
 API analysis for functional test case design - http://wiki.meego.com/Quality/TestSuite MCTS/MCTS_API_analysis)
 Coverage analysis spreadsheets - http://gitorious.org/qa-tools/mcts-coverage
 Example of test specification of MCTS test suite - http://wiki.meego.com/QualityTestSuiteVideo_Playback_Driver_Test_Specification
 Template for test plan - http://wiki.meego.com/CompTestPlanTemplate)