Firefox OS/MoztrapGuideline: Difference between revisions
Jump to navigation
Jump to search
| Line 32: | Line 32: | ||
* '''Tags''' | * '''Tags''' | ||
** Test case with tags like [https://moztrap.mozilla.org/manage/cases/?filter-id=6887 v1.1], [https://moztrap.mozilla.org/manage/cases/?filter-id=15056 v2.1] means the cases were created since Firefox v1.1 or v2.1 respectively. | ** Test case with tags like [https://moztrap.mozilla.org/manage/cases/?filter-id=6887 v1.1], [https://moztrap.mozilla.org/manage/cases/?filter-id=15056 v2.1] means the cases were created since Firefox v1.1 or v2.1 respectively. | ||
** Use proper [https://moztrap.mozilla.org/manage/tags/ tags] to describe your case, easy for searching and categorization. | |||
** Sample: [https://moztrap.mozilla.org/manage/cases/?filter-id=15054 #15054] | |||
* '''Moztrap Suite''' | * '''Moztrap Suite''' | ||
| Line 67: | Line 69: | ||
* [https://moztrap.mozilla.org/manage/suites/?&pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-name=%5Brat%5D [RAT<nowiki>]</nowiki>] prefix | * [https://moztrap.mozilla.org/manage/suites/?&pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-name=%5Brat%5D [RAT<nowiki>]</nowiki>] prefix | ||
** Release acceptance test - contains [http://en.wikipedia.org/wiki/Happy_path happy cases] | ** Release acceptance test - contains [http://en.wikipedia.org/wiki/Happy_path happy cases] | ||
== When to do what == | == When to do what == | ||
Revision as of 09:48, 27 November 2014
General Info
- Moztrap General
- MozTrapHelper by Shing - recommend to add this to your Firefox browser.
Test case creation
- Test case creation primer - read this before creating test cases^^
- All-pairs testing - Test all possible discrete combinations of those parameters without lots of redundant cases.
- General
- Tool
- Perl script or Windows executable - input parameter options, it shows the cases needed for testing a feature.
- Sample
Test case priority
- 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
- Tags
- 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 | [Media PF] | [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 |
- [Small set] prefix
- Case can be tested in short time
- [RAT] prefix
- Release acceptance test - contains happy cases
When to do what
- Case creation and maintenance
- Test cases for current master
- Usually created before FL, keep maintaining by current function owners.
- Test cases for other branches
- Maybe created by partners or added because of regression found or just missing test coverage
- Keep maintaining by partners or by current function owners.
- Test cases for bugs or added because of regression found
- Keep maintaining by current function owners.
- Test cases for current master
- Invalid/redundant cases - how to?
- How to spot them?
- Scout around?
- Go through all cases?
- Using keyword/tag search to find issue?
- Reported by partner or people who runs cases everyday (big thanks!)
- Maintenance
- Just updating them by yourself or
- Pass them to functional area owners to review and to update.
- How to spot them?
Improvement
Search link, Submit a new bug for Moztrap
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);