QA/TCM/Documentation

Glossary

• Product:
  • Products can be thought of as a Product Line, without version. 
  • i.e.: Firefox, Thunderbird, Fennec, etc
  • Persistent: Considered persistent because presumably, we will continue making new versions indefinitely.
• Test Cycle:
  • These cycles are to test a version of the product from beginning to end. 
  • i.e.: Firefox 4.0, Firefox 5.0, Fennec 4.0, etc
  • Transient: Considered transient because it has a life that will come to an end when the product has shipped, or end of life'd.
• Test Run:
  • These represent specific testing tasks for a phase of a Test Cycle.
  • i.e.: Smoke, Aurora, Beta, I10n, Stress
  • Transient (Green): Considered transient because it also has a life that will come to an end when the run has been completed
• Test Plan:
  • Test plans are a collection of Test Suites and can be added to Test Runs.  A Test Plan can be used as a template for acreating a new Test Run.  However, a Test Run can be built from more than on Test Plan, if the admin chooses.
  • i.e.: Beta, Aurora, L10n, Stress
    
• Test Suite:
  • A collection of Test Cases.  These generally represent a feature. Or particular types of tests.
    
  • In Litmus, these are called Test Groups
  • i.e.: Tabs, Video, HTML5, Smoketests, L10n, Flash
    
• Test Case:
  • A collection of steps to test a particular function.
  • i.e.: Pause Flash Video, Enter/Exit Full Screen Mode, Create new Tab
    
• Test Step / Exp Result:
  • Each step has its own Expected Result.  This can be blank for any steps that don't have an expected result as part of the test.
  • i.e.: Click File / New Tab
    

Persistent Object Hierarchy

Transient Object Ownership Hierarchy