Litmus:Todo: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(38 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Litmus ToDo List =
'''[[Litmus|« back to Litmus main page]]'''
 
= Litmus To-Do 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.  
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.  
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Webtools&component=Litmus&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=DUPLICATE&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All Open Litmus Bugs]
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Webtools&component=Litmus&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=ASSIGNED&resolution=DUPLICATE&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All Assigned Litmus Bugs]


== Unclaimed Tasks ==
== Unclaimed Tasks ==
* Administration Interface
 
* Bugzilla User Integration
* '''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.
* Attachments
 
* New features created by schema
* '''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 entire 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 are the same.
** 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 ==
== Claimed Tasks ==
Line 20: Line 18:
=== Chris Cooper ===
=== Chris Cooper ===
* In Progress
* In Progress
** Reporting/Querying
** [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Webtools&component=Litmus&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=ASSIGNED&resolution=DUPLICATE&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=ccooper%40deadsquid.com&emailassigned_to2=1 Litmus bugs currently assigned to coop]
*** There needs to be some way to query the testcases and view them in a list format. [http://www.zachlipton.com/litmusmockups/confirmedfailures.html Here's a very rough mockup]. [[User:Zachlipton|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
* Completed Tasks
** New Schema
** Litmus i18n
 
** '''Test Runs''': this is the major piece that is present in Testrunner but still missing in Litmus. Design is listed in [[Litmus:Design#Replicate_Testrunner_Functionality]].
=== Jay Patel ===
** '''Updated reporting tools''': since these tools need to know about test runs anyway, I'm taking this opportunity to update them as well.
** '''Administration Interface'''
** '''Testcase/Subgroup/Testgroup Management'''
** add "Search for testcase" functionality -> search by: testgroup, subgroup, product
** added full-text search (by summary, steps, expected results)
** database re-architect for test runs;
** add group listing (i.e. this testcase belongs to the following groups)
** only display testcases that are not marked as obsolete to regular testers. Admin can see all testcases.
** script to grab/update test cases from Testrunner
*** add Testrunner ID and version fields to Litmus tests table
** get litmus mailing alias setup
*** we're going to tag along on the existing dev-apps-webtools@lists.mozilla.org mailing list
** '''Litmus Roadmap'''
*** milestones + dates for version 1.0 and beyond
** '''Reporting/Querying'''
** '''New Schema'''
** '''UI Improvement'''
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=302688 bug 302688]
** '''Multiple comments and bug numbers per test result'''
** '''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
*** comment icons à la tinderbox
** fix the percentage system used for running tests
*** make percentages based on build ID, rather than time
*** display community coverage percentages as well as personal percentages


=== Zach Lipton ===
=== Zach Lipton ===


* In Progress
* In Progress
** Add/clone testcase
** QMO Extension
** Web Services Interface
** [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&product=Webtools&component=Litmus&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=ASSIGNED&resolution=DUPLICATE&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=zach%40zachlipton.com&emailassigned_to2=1 Litmus bugs currently assigned to zach]
*** Need to have a XML-RPC/SOAP/REST/whatever interface to Litmus to get tests, submit results, etc... [[User:Zachlipton|Zachlipton]] 09:15, 10 Aug 2005 (PDT)
** UI Improvement
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=302688 bug 302688]


* Completed Projects
* Completed Projects
** The testdata filter
** '''User info''': personal pages for testers where they can change their information.
** '''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. [[User:Zachlipton|Zachlipton]] 11:03, 28 Jul 2005 (PDT)
*** 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. [[User:Zachlipton|Zachlipton]] 11:03, 28 Jul 2005 (PDT)
** litmusconfig.js
** '''litmusconfig.js'''
*** Select boxes need to be converted to pull data from litmusconfig.js rather than the clunky show/hide div approach. [[User:Zachlipton|Zachlipton]] 15:47, 29 Jul 2005 (PDT)
*** Select boxes need to be converted to pull data from litmusconfig.js rather than the clunky show/hide div approach. [[User:Zachlipton|Zachlipton]] 15:47, 29 Jul 2005 (PDT)
** Precompile templates
** '''Precompiled templates'''
** '''Authentication''': 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:
*** '''Status''': Initial version checked into CVS 1/7/06. Working on migration to allow user accounts from the previous system to be used under the new authentication system.
** '''Update Documentation'''
*** How to checkout Litmus from CVS doc on wiki
*** Update README
*** Update INSTALL
*** Update auth information on wiki and add API description
** '''User management''': admin tools for working with user accounts;
** '''Web Services Interface - Design'''
*** Need to have a XML-RPC whatever interface to Litmus to get tests, submit results, etc...

Latest revision as of 14:42, 15 October 2007

« back to Litmus main page

Litmus To-Do 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

  • 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.
  • 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 entire 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 are the same.

Claimed Tasks

Chris Cooper

  • Completed Tasks
    • Litmus i18n
    • Test Runs: this is the major piece that is present in Testrunner but still missing in Litmus. Design is listed in Litmus:Design#Replicate_Testrunner_Functionality.
    • Updated reporting tools: since these tools need to know about test runs anyway, I'm taking this opportunity to update them as well.
    • Administration Interface
    • Testcase/Subgroup/Testgroup Management
    • add "Search for testcase" functionality -> search by: testgroup, subgroup, product
    • added full-text search (by summary, steps, expected results)
    • database re-architect for test runs;
    • add group listing (i.e. this testcase belongs to the following groups)
    • only display testcases that are not marked as obsolete to regular testers. Admin can see all testcases.
    • script to grab/update test cases from Testrunner
      • add Testrunner ID and version fields to Litmus tests table
    • get litmus mailing alias setup
      • we're going to tag along on the existing dev-apps-webtools@lists.mozilla.org mailing list
    • Litmus Roadmap
      • milestones + dates for version 1.0 and beyond
    • Reporting/Querying
    • New Schema
    • UI Improvement
    • Multiple comments and bug numbers per test result
    • 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
      • comment icons à la tinderbox
    • fix the percentage system used for running tests
      • make percentages based on build ID, rather than time
      • display community coverage percentages as well as personal percentages

Zach Lipton

  • Completed Projects
    • User info: personal pages for testers where they can change their information.
    • 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
    • Authentication: 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:
      • Status: Initial version checked into CVS 1/7/06. Working on migration to allow user accounts from the previous system to be used under the new authentication system.
    • Update Documentation
      • How to checkout Litmus from CVS doc on wiki
      • Update README
      • Update INSTALL
      • Update auth information on wiki and add API description
    • User management: admin tools for working with user accounts;
    • Web Services Interface - Design
      • Need to have a XML-RPC whatever interface to Litmus to get tests, submit results, etc...
Retrieved from "https://wiki.mozilla.org/index.php?title=Litmus:Todo&oldid=71115"