Litmus:Todo: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 7: Line 7:
* Bugzilla User Integration
* Bugzilla User Integration
* Attachments
* Attachments
* Suites
** Litmus needs to support the creation of test suites, a arbitrary ordered collections of individual tests, subgroups, and testgroups. [[User:Zachlipton|Zachlipton]] 08:49, 8 Aug 2005 (PDT)
* New features created by schema
* New features created by schema
** Coop's new schema has paved the way for some additional features for us to support. These include:
** Coop's new schema has paved the way for some additional features for us to support. These include:
Line 14: Line 16:
**** Take advantage of the test_result_bugs table and the tests.regression_bug_id column to allow users to link tests and testresults with bugs.  
**** Take advantage of the test_result_bugs table and the tests.regression_bug_id column to allow users to link tests and testresults with bugs.  
*** Log File Support
*** Log File Support
**** Build UI for the fields created in test_result_logs.  
**** Build UI for the fields created in test_result_logs.


== Claimed Tasks ==
== Claimed Tasks ==

Revision as of 02:36, 7 September 2005

Litmus ToDo List

Here's some things that Litmus needs. If you feel like taking one of these tasks on, great! Just post about your progress on this page.

Unclaimed Tasks

  • Administration Interface
  • Bugzilla User Integration
  • Attachments
  • Suites
    • Litmus needs to support the creation of test suites, a arbitrary ordered collections of individual tests, subgroups, and testgroups. Zachlipton 08:49, 8 Aug 2005 (PDT)
  • New features created by schema
    • Coop's new schema has paved the way for some additional features for us to support. These include:
      • Support for multiple comments per testresult.
        • Currently we place the contents of the "notes" field provided at result submission time into a new comment and attach it to the test result, but there needs to be a way for other users to add additional comments later. These comments need to be displayed in show_test.cgi, and be searchable.
      • Bugzilla Bug Integration
        • Take advantage of the test_result_bugs table and the tests.regression_bug_id column to allow users to link tests and testresults with bugs.
      • Log File Support
        • Build UI for the fields created in test_result_logs.

Claimed Tasks

Chris Cooper

  • In Progress
    • Reporting/Querying
      • There needs to be some way to query the testcases and view them in a list format. Here's a very rough mockup. Zachlipton 14:40, 27 Jul 2005 (PDT)
      • determine what other reporting functions we need, and how QA people need to be able to view/sort those results.
  • Completed Tasks
    • New Schema

Jay Patel

Zach Lipton

  • In Progress
    • Add/clone testcase
    • Web Services Interface
      • Need to have a XML-RPC/SOAP/REST/whatever interface to Litmus to get tests, submit results, etc... Zachlipton 09:15, 10 Aug 2005 (PDT)
    • UI Improvement
  • Completed Projects
    • The testdata filter
      • The testdata filter (in Template.pm) is in pretty bad shape and needs to get fixed. It likely opens us up to XSS attacks if we actually had a real cookie to attack. Zachlipton 11:03, 28 Jul 2005 (PDT)
    • litmusconfig.js
      • Select boxes need to be converted to pull data from litmusconfig.js rather than the clunky show/hide div approach. Zachlipton 15:47, 29 Jul 2005 (PDT)
    • Precompile templates