CSC/ECE 517 Fall 2009/program2 buddi wn

Buddi Project

Objectives

Functionality

1. Verify that splits in the data model have been implemented correctly. Ensure that the API wrapper functions allow transparent access to the model. Ensure that there are no edge cases where data corruption occurs.
2. Refine and complete the view layer, and verify that it works as desired in all cases.

Testing

• Verify Model using JUnit.

There are already some model and API tests in the junit source folder - you can use these as a basis for creating more. You should construct some tests to only test the model, others to test the plugin API, and still others to verify that changes written to the API are accessible to the model (and vice-versa).

Be sure to test the edge cases and exceptional input, for instance: what happens if you try to split a transaction 1000 ways? What happens if you try to include 0 splits? What happens when you try to pass null to various setter methods?

• Verify UI

Using your understanding gained from the model tests, you must construct written documents detailing what tests you are planning on doing, and how you plan to go about them. You must then carry out these tests, and document the results. In addition to data integrity, the view tests should include a usability component - is the way which split transactions are expressed intuitive? Are there better ways to do this?

Bugs or Undesired Behaviors

Title	Details	Actual Behavior	Expected Behavior	Solved
Create New menu	Undesired behavior. Create new options shouldn't be put under Edit menu. It's not intuitive for new users.	Under My Accounts tab, Edit -> Create Account. Under My Budget tab, Edit -> Create Budget Category.	Several options: Move to under File menu Create button for "New Account" and "New Budget Category"	No
The "+", "-" buttons didn't appear naturally until one switched the focus TWICE after entering the amount.				No
				No

Useful Links

1. Buddi docs for Developers
2. Buddi docs for Users