Issue Capturer

Description

The Issue Capturer web interface will save information on issues and comments on particular features of a program submitted by users. This will provide the developers with a large and diverse amount of insight into how their application is received and to identify bugs.

The Issue Capturer desktop application will be used to view issue information that has been previously saved.

The technologies used to develop Issue Capturer have been chosen to introduce beginner developers to various programming environments, techniques, and tools.

The Project Page can be found here

Features

The features of the web application include:

User Inputs:

The name of the feature or process they are testing and its reference number.
The ability to input their name and their email address.
The operating system they are using. Selected from a list.
The web browser they are using and the browser version. Selected from a list.
Where in the program the test failed.
A description as to how the program failed.
Detailed steps up to the point at which the program failed.
Any additional information that the user deems important.
The date of submission.

Upon completion of form entry:

Click a "Save" button, which will take them to a page which notifies them that their submission has been received.
Click "Cancel" button, which will return them to the home page without submitting the information.

When the system receives the results from the user:

server side and client side CGI validates input.
The input data is saved to a database.
the system will send a notification if the data entry has succeeded or failed.

A page where the administrator can create and edit test profiles as well as update. That contains:

A field for the name of the feature.
A field for the reference number of the test.
A field for the description of the nature of the test.
A field for the steps involved in order to conduct the test.
A "Save" button to save that test.
An "Edit" button to modify existing tests.
A delete button to delete tests that are outdated or no longer necessary.
A way to return to the main page.

Pages where the administrator can edit browser and OS information

simple add and delete functionality

Features of the desktop application:

Displays the results obtained by the web application.
Is able to export the result to a spreadsheet for further analysis.

Prototype Pages

These prototypes are in no way final and are subject to much improvement. They do give a rough estimation on how the application will flow.
The pages will be accessed starting with the main page. From there the user will have the option of going to a How-To page explaining the use of the application and then returning to the main page or going to the Form Entry page. When they submit the form, a notification will appear. If successful, it will ask them if they want to submit another form. If unsuccessful, notifies them of the failure and asks them to resubmit.