QA/Litmus Redesign/Administrator Work Flows

From MozillaWiki
Jump to navigation Jump to search

<< Back to the Design Center

Administrator Work Flows

Test case Vetting Workflow

  • Need reminder/notification of test cases that need vetting

Test Review Process

  • Able to optionally instantiate test reviews for submitted test cases from community
    • Able to give feedback and decide test case needs more work
    • Able to approve test case and include it in system
    • Able to designate users as "not needing review"
  • Have ability to search for testcases and display them in a good, easy to read format where you can drill down on each case and go back to the list without any hassle.
  • Have ability on per project basis default the user's "submitted testcase needs review" bit to false/true as the project admin desires.
  • Notification/reminder system for test cases that need review.

User Creation

  • Be able to create other administrators for either top-level litmus wide administration, or project wide administration, or as end-users.
    • End-Users should still be able to create test cases, but if the user does not have the "ok to submit" bit cleared then the testcase will be flagged for review.

Migrating Between Branches of a Product

  • Migration work flow must exist and not involve giant database copies
    • However, must also have option to fork a testcase in the future - for example, in most migrations, testcases will not need any modification of their steps or results from their incarnation in the previous version of the product. But if between version x and version y the test case must change for new behavior in version y then we must fork the test case at that point.