Backlog

Here's a backlog of feature ideas. In rough order or interest or importance. If you're interested in one of these, let us know! These are just ideas, not commitments by anyone to implement anything on this list.

Users have logins	Currently being implemented in the "security" branch
Users have permissions	Currently being implemented in the "security" branch
Users have profile defaults	Currently being implemented in the "security" branch
Test runs indicate whether they are "In Progress" or "Done"	Statistics wouldn't be calculated until all the results have been submitted and a test run was marked "Done". Submitting to a project marked "Done" would result in an error. Ant task by default would mark test run as "done" on submission, but could be toggled via a task property.
Users have views
Selenium test suite for browser regression testing	Selenium Test Ideas
The analysis table polls for updates	The analysis table could poll periodically to see if any of the test run's analyses have been updated. This would also be useful to prevent update collisions (which would result in transaction exceptions) where multiple people update the same test analysis. The javascript app would need to get metadata back along with the test run to know what time that query was executed (this may required a 'lastModified before now' clause being added to queries). Then when polling it would just ask for the IDs of outcomes that have been updated since lastModified. If any of those IDs are currently being displayed on the table, an ajax request would be made to update them. Perhaps the row would be highlighted for a moment to indicate that the data had updated. The built-in polling for YUI datatables won't work for us in this scenario based on my research.
User can move test runs in bulk	User can move test runs to a different project. Sometimes as a result of errors, a test run is submitted to the wrong project. It'd be nice to have a way to move a test run to a different project.
Use can delete test runs in bulk
A user can search the analysis table for highlighted text in the output dialog	A common workflow seems to be to look at the output dialog for some distinguishing search term, close the dialog, then search for that output term. One workflow discussed was User highlights text in the output dialog User clicks "Search" button (naming TBD) Output dialog closes and the analysis table is automatically put into search mode for the highlighted output.
Make URL taglib	(Development task) Currently urls.gsp is used as a way to transfer URLs from the cuanto app into javascript, so you have to render that entire file anywhere you want to use a cuanto-specific URL (used for ajax requests). It's nice to have them all in a centralized place, but overkill if you only want one url. I think a viable alternative might be to create our own taglib that we could use to render individual URLs. Something like: `<cuanto:url alias="testRunOutcomes"/>` And then you could use those tags to just render the URLs you want on the GSPs you want, rather than just including them all.
User can apply analysis to most recent outcome in test case history view
email sent to address when new results are added
UI for manually uploading result files
Generate test suites based on failures	I'm not sure how feasible this would be, we'd probably have to expand the notion of test parsers into test plugins, where each plugin knew how to output a suite for it's test type.
twitter notifications	Or other short message-type service.
Support Internationalization	This story would be to move all messages into message bundles. This includes GSPs, javascript. Also you might consider a way to internationalize the domain objects that are "pre-set" in the app, like FailureReason/AnalysisState and TestResult
Allow bug system plug-ins	If you could visually see from the analysis tool if a bug associated with a particular test case is still active, resolved fixed, by design, etc., this would speed analysis. This comes in handy above when an old failure still fails, but with a quick glance, you can see the bug associated with it shows resolved fixed. Then you know some investigation is likely needed.
Multi-criteria search	Allow filtering a dataset by multiple criteria, e.g. owner and note, owner OR not etc.
Link test failures and errors to test code in fisheye	Or could it just be linking test cases to code in a repository browser? Maybe a TestLinkPlugIn interface like Then could implement TestLinkPlugIn for fisheye, GitHub, other URI-accessible code browsers.