Litmus:Todo

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: there is currently no authentication in Litmus. We accept the first email address the user provides when testing, use this to build a cookie, and then never let them change it (without removing the cookie, of course). We need to implement proper authentication:
  • mirror existing Bugzilla login information. This should be synced at some regular interval;
  • allow users to login/logout from within Litmus;
  • auto-populate all email fields with current credentials from cookie when present;
  • redirect through login screen when login credentials are not present;
  • redirect users without Bugzilla accounts to Bugzilla.

• Attachments: do we still have a need for attachments? We're not trying to replace Bugzilla here, and there's a pretty high potential for abuse. We might want to allow this for community proposals for changes to test cases.

• Bugzilla Bug Integration: automatically mark-up bugs numbers in comments and test steps/expected results as links to Bugzilla.

• Log File Support: Build UI for display of result logs, which will now be held in the database to facilitate comparison.

• Test list add/edit/clone: need to be able to create new test lists, add/edit/reorder test cases within that test list, and also clone existing test lists to make it easier to add new lists.

• Test result/run comparison: we need to be able to compare single test results head-to-head, and we also need to display comparisons between entri test runs. We can take a page from LXR's book and mark up the deltas in special colors to facilitate comparisons. We might also want to use some AJAX to roll-up the parts of the comparison that don't differ.

• Backup/Archive/Purging of old test results: the first step here will be to determine what our data retention policy will be. Both Bob and Tracy have said that they never need to go back further than one month to compare test results, but their opinions might change if it were easier for them to do so. It might make sense to be able to tag particular test runs, e.g. test runs for releases, with a DO_NOT_PURGE flag so that they can be kept around indefinitely.

Claimed Tasks

Chris Cooper

• In Progress
  • Migration of New Firefox 1.5 BFTs from Testrunner to Litmus
  • General Litmus cleanup prior to community testing debut of Litmus
    • no results text for statistics
    • improve front page UI: login box, make results display less wide, interim logout functionality
  • Test Runs - Design: this is the major piece that is present in Testrunner but still missing in Litmus. I will add my design to Litmus:Design#Replicate_Testrunner_Functionality, at which point I should have many smaller subtasks to add to the unclaimed task pool above. At the very least, we will need the basic add/edit/clone functionality.

• Completed Tasks
  • Reporting/Querying
  • New Schema
  • UI Improvement
    • bug 302688
  • Multiple comments and bug numbers per test result

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)

• 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)
  • Precompiled templates