Differences between revisions 2 and 3
Revision 2 as of 2008-09-19 17:57:06
Size: 3807
Editor: cabernet
Comment:
Revision 3 as of 2008-09-19 18:00:45
Size: 3887
Editor: cabernet
Comment:
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:

. attachment:CyAutoBugReportDialog.JPG

. attachment:CyAutoBugContents.JPG

RFC Name : …

Editor(s): …

Date: …

Status: …

TableOfContents([2])

Proposal

Automatic error detecting and reporting has become common practice in desktop application and web-based application. The bugs found in the filed may be those that would never be caught during testing. With an automatic bug report system, to file a bug report is just a click on a button on a dialog, therefore bug-reports from various kinds of users become possible, including those non-technical and won’t bother to login to bug tracker and file a detailed report.

Cytoscape should also have such automatic bug reporting system, which would potentially increase more feedbacks from Cytoscape users and help developers to fix the bugs. This RFC describes how to build an automatic bug reporter for Cytoscape.

Use Cases

1. GUI mode

Scenario: A user is using Cytoscape for a while and suddenly Cytoscape runs into a problem. An exception is caught and the exception is classified as a bug. A dialog box pops up and asks user if he/she wants to report the error to Cytoscape. If user says “Yes”, information about the bug will be sent to Cytoscape bug tracker.

. attachment:CyAutoBugReportDialog.JPG

. attachment:CyAutoBugContents.JPG

2. Headless mode

Cytoscape is running in headless mode and the mode is “interactive”, not “server”. When an exception is caught and the exception is classified as a bug, a message on the console will tell the user what happened and ask the user if he/she wants to report the error to Cytoscape. If user says “Yes”, information about the bug will be sent to Cytoscape bug tracker.

3. Do not report any bug

In the case that a user decides not to report any error, the user has the option to set the property value “automaticErrorReport” (true, by default) to false and Cytoscape will remember the decision.

Implementation Plan

Outline and describe the process and major issues related to implementing this proposal. Illustrate your plan when possible. Try this free online tool for making diagrams -> [http://www.best4c.com/editor/NetMapApplication.jsp Best4c] (draw; save; then insert hyperlink into this page)

Project Management

Project Timeline

Provide a timeline for implementation. Insert a graphic if you can. Try this free online tool for making project timelines -> [http://www.helpuplan.com/index.asp Help-u-Plan] (create a new chart; modify; right-click to save gif; then attach to this page)

Tasks and Milestones

Outline the major milestones and tasks involved in implementation.

  1. Milestone 1: …

    1. Task 1: ...
    2. Task 2: ...
  2. Milestone 2: …

Project Dependencies

Outline and projects that depend on this project, link to relevant RFC's and note at what point dependent projects could be started.

Link to other related RFCs

Issues

List any issues, conflict, or dependencies raised by this proposal

Comments

  • Add comment here…

How to Comment

Edit the page and add your comments under the provided header. By adding your ideas to the Wiki directly, we can more easily organize everyone's ideas, and keep clear records. Be sure to include today's date and your name for each comment. Try to keep your comments as concrete and constructive as possible. For example, if you find a part of the RFC makes no sense, please say so, but don't stop there. Take the extra step and propose alternatives.

AutomaticBugReporter (last edited 2009-02-12 01:03:36 by localhost)

Funding for Cytoscape is provided by a federal grant from the U.S. National Institute of General Medical Sciences (NIGMS) of the Na tional Institutes of Health (NIH) under award number GM070743-01. Corporate funding is provided through a contract from Unilever PLC.

MoinMoin Appliance - Powered by TurnKey Linux