Meego Wiki
Views

Quality/TestSuite/MCTS/MCTS Development Guideline

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→MeeGo Core Test Suite(CTS) Development Guideline)
Line 1: Line 1:
-
== '''MeeGo Core Test Suite(CTS) Development Guideline''' ==
+
== '''MeeGo Core Test Suites(CTS) Development Guideline''' ==
=== '''Test Definition''' ===
=== '''Test Definition''' ===
* XML format :http://gitorious.org/qa-tools/test-definition
* XML format :http://gitorious.org/qa-tools/test-definition
Line 55: Line 55:
*** Test most critical functionalities  
*** Test most critical functionalities  
*** With most typical parm-pairs
*** With most typical parm-pairs
 +
 +
Test package list see http://wiki.meego.com/MeeGo_Core_Test_Suites_Packaging_draft

Revision as of 14:41, 9 June 2010

Contents

MeeGo Core Test Suites(CTS) Development Guideline

Test Definition

Test Case Naming

  • Show the purpose clearly, avoid simply use number.
  • Name length should less than 30
  • Use '_' to connect words

File header

  • Copyright
  • License
  • Author
  • Changelog

Check list

  • README
  • src/ : contain source files
  • utils/: contain utility and tools if any
  • Makefile
  • tests.xml
  • data/: contain small data files (For big data such as media content, need separate package)
  • pack.sh: the script to make package
  • test.spec: spec files to create package

Makefile (??? If need automake)

  • make : build test suite.
  • make install: install test binary or script into /usr/bin, and tests.xml into /usr/share/<testpackagename>/tests.xml
  • make clean: remove all object file and tempory files
  • make uninstall: remove test binary, scripts, and tests.xml out of target installation directory.
  • make package: create rpm package

Coding Style

Test Case Design

  • Common Rule:
    • Automate test under condition of stability
    • Main function should keep simple and structure keep neat.
    • Define common function file shared between test cases.
    • Has no dependency on other test case.
    • Has no dependency on UX or vertical specific apps.
    • Has no dependency on test framework.
    • Platform irrelevant
    • Clean environment after test complete.
    • If parameters number greater than 3, use getopts
    • Enough comments
  • Test Coverage Category Rules:
    • Thorough
      • Cover all APIs.
      • Test case targets for usage (API combination) instead of single API.
      • With Parm-pairs of equivalence partitioning and boundary condition (All-pairs optional)
    • Average
      • High risk APIs(e.g. new functionality relevant APIs) should be covered with thorough test rules
      • Legacy or low risk APIs are covered only with positive tests
    • Lightweight
      • Test most critical functionalities
      • With most typical parm-pairs

Test package list see http://wiki.meego.com/MeeGo_Core_Test_Suites_Packaging_draft

Retrieved from "http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Development_Guideline"
Personal tools