Canmove, confirm
2,850
edits
Changes
no edit summary
== Unclaimed Tasks ==
* '''Administration Interface''': allow admins to edit supporting entities — products, groupsplatforms, subgroupsopsyses, etc... others? — without having to manually edit the database tables.
* '''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.
* '''Log File Support''': Build UI for display of result logs, which will now be held in the database to facilitate comparison.
* '''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.
* '''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.;
* '''Testcase StateUser management''': replace the current state display (broken) admin tools for working with a state matrix/table that displays testcase state for each branch and platform. Must also reference Build ID.use accounts;
* '''Search for TestcaseUser info''': by name, group, personal pages for testers where they can change their information and subgroupview personal testing stats. Any other searchable fields?
== Claimed Tasks ==
* In Progress
** '''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.
** get metadata for Bob's automated tests into the database** '''Web Services Interface - DesignTestcase/Subgroup/Testgroup Management'''*** Need to have Zach has provided a XML-RPC whatever simple Enter Test interface to Litmus to get tests, submit results, etc...** add group listing (i.e. I will be extending this testcase belongs over the next few days to perform all the following groups)management functions we need.** add "Search for testcase" functionality -> search by: nametestgroup, testgroupsubgroup, product
* Completed Tasks
** 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
* In Progress
** '''Add/clone testcaseWeb Services Interface - Design'''*** '''Status''': Initial template work done. Need to complete CGI and add authenticationhave a XML-RPC whatever interface to Litmus to get tests, submit results, etc.. Expected to be completed by 1/18/06 or so.
** '''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.
