Firefox OS/MoztrapGuideline: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 61: Line 61:
*** http://en.wikipedia.org/wiki/All-pairs_testing
*** http://en.wikipedia.org/wiki/All-pairs_testing
*** http://www.pairwise.org/
*** http://www.pairwise.org/
*** http://www.testingeducation.org/wtst5/PairwisePNSQC2004.pdf
** Tool
** Tool
*** [http://www.satisfice.com/tools.shtml Perl script or Windows executable], it shows the cases needed for testing a feature without lots of redundant cases.
*** [http://www.satisfice.com/tools.shtml Perl script or Windows executable], it shows the cases needed for testing a feature without lots of redundant cases.

Revision as of 04:49, 24 November 2014

Work on Moztrap

Test case priority

Link

  • Define test case’s priority
    • P1 - Feature smoketests
    • P2 - Feature basic functional tests
    • P3 - Boundary, edge, stress test cases
    • P4 - Anything else that doesn't fall in the above buckets

Organize cases

  • Mindmap
    • Use a mind map to show the structure of your test cases, mindmup integrates with Google drive, permission also controlled by Google drive.
    • Sample: v2.1 contacts new features
    • Test case with tags like v1.1, v2.1 means the cases were created since Firefox v1.1 or v2.1 respectively.
  • Moztrap Suite

Put functional prefix before suites.

Functional Prefix Example
Communications [Comms] [Comms]Dialer
Device [Device] [Device] Media Transfer Protocol
Bluetooth [BT] [BT]Bluetooth
Media [Media] [Media]Gallery
Multimedia Platform [BT]Bluetooth [Media PF]WebRTC P2P
Networking/Connectivity [RIL] [RIL]SimToolKit
Productivity [Prod] Example
System Front-End [Sys FE] Example
System Platform [Sys PF] [Sys PF]Airplane Mode
Services [Service] Example
Performance & Metrics [Perf] Example

Test case creation

Improvement

Search link

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);