CSC/ECE 517 Fall 2009/program2 buddi wn - Revision history

Tinydancer: /* Important Information */

2009-10-26T19:45:30Z

Important Information

← Older revision		Revision as of 19:45, 26 October 2009
Line 2:		Line 2:

	== Important Information ==		== Important Information ==
	* Submission: October 23 (~~Friday~~)		* Submission: October 26 (Monday)
	* First Feedback: October 30 (Friday)		* First Feedback: October 30 (Friday)
	* Resubmission: November 6 (Friday)		* Resubmission: November 6 (Friday)

Kanke: /* Required Results */

2009-10-25T21:05:28Z

Required Results

← Older revision		Revision as of 21:05, 25 October 2009
Line 18:		Line 18:
	The following is required for your results:		The following is required for your results:
	# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).		# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).
	# A '''written report ([[Written Report on Model %28Testing%29\|W]]) on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)		# A '''written report ([[Written Report on Model %28Testing%29\|Model]]) on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)
	# A w'''ritten report ([[Written Report on View %28Testing%29\|W]]) on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.		# A w'''ritten report ([[Written Report on View %28Testing%29\|View]]) on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.
	# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.		# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.

Tinydancer: /* Bugs or Undesired Behaviors */

2009-10-23T00:09:04Z

Bugs or Undesired Behaviors

← Older revision		Revision as of 00:09, 23 October 2009
Line 66:		Line 66:
	\| It shows <From> in an unselected mode		\| It shows <From> in an unselected mode
	\| Should show "split" entry with "..." button surfaced		\| Should show "split" entry with "..." button surfaced
	~~\| No~~
	~~\|-valign="top"~~
	~~\| ADDITIONAL FEATURE: Add Semi Year (twice a year) "Budget Period Type".~~
	~~\| From "My Budget" tab, "Edit" -> "Modify Budget Category" -> "Budget Period Type".~~
	~~\| No option for Semi Year~~
	~~\| Add the functionality~~
	\| No		\| No
	\|-valign="top"		\|-valign="top"

Kanke: /* Required Results */

2009-10-20T14:59:53Z

Required Results

← Older revision		Revision as of 14:59, 20 October 2009
Line 19:		Line 19:
	# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).		# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).
	# A '''written report ([[Written Report on Model %28Testing%29\|W]]) on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)		# A '''written report ([[Written Report on Model %28Testing%29\|W]]) on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)
	# A w'''ritten report([[Written Report on View %28Testing%29\|W]]) on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.		# A w'''ritten report ([[Written Report on View %28Testing%29\|W]]) on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.
	# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.		# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.

Kanke: /* Required Results */

2009-10-20T14:59:30Z

Required Results

← Older revision		Revision as of 14:59, 20 October 2009
Line 18:		Line 18:
	The following is required for your results:		The following is required for your results:
	# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).		# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).
	# A '''written report ([[Written Report on Model %28Testing%28\|W]]) on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)		# A '''written report ([[Written Report on Model %28Testing%29\|W]]) on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)
	# A w'''ritten report([[Written Report on View %28Testing%28\|W]]) on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.		# A w'''ritten report([[Written Report on View %28Testing%29\|W]]) on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.
	# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.		# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.

Kanke at 14:58, 20 October 2009

2009-10-20T14:58:33Z

← Older revision		Revision as of 14:58, 20 October 2009
Line 18:		Line 18:
	The following is required for your results:		The following is required for your results:
	# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).		# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).
	# A '''written report[[~~http://pg-server.csc.ncsu.edu/mediawiki/index.php?title=Written_Report_on_Model_~~%28Testing%29 W]] on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)		# A '''written report ([[Written Report on Model %28Testing%28\|W]]) on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)
	# A w'''ritten report[[~~http://pg-server.csc.ncsu.edu/mediawiki/index.php?title=Written_Report_on_View_~~%28Testing%29 W]] on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.		# A w'''ritten report([[Written Report on View %28Testing%28\|W]]) on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.
	# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.		# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.

Kanke: /* Required Results */

2009-10-20T14:00:26Z

Required Results

← Older revision		Revision as of 14:00, 20 October 2009
Line 19:		Line 19:
	# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).		# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).
	# A '''written report[[http://pg-server.csc.ncsu.edu/mediawiki/index.php?title=Written_Report_on_Model_%28Testing%29 W]] on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)		# A '''written report[[http://pg-server.csc.ncsu.edu/mediawiki/index.php?title=Written_Report_on_Model_%28Testing%29 W]] on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)
	# A w'''ritten report[[~~Written Report on View (Testing)~~]] on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.		# A w'''ritten report[[http://pg-server.csc.ncsu.edu/mediawiki/index.php?title=Written_Report_on_View_%28Testing%29 W]] on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.
	# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.		# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.

Kanke: /* Required Results */

2009-10-20T13:59:33Z

Required Results

← Older revision		Revision as of 13:59, 20 October 2009
Line 18:		Line 18:
	The following is required for your results:		The following is required for your results:
	# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).		# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).
	# A '''written report[http://pg-server.csc.ncsu.edu/mediawiki/index.php?title=Written_Report_on_Model_%28Testing%29 W] on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)		# A '''written report[[http://pg-server.csc.ncsu.edu/mediawiki/index.php?title=Written_Report_on_Model_%28Testing%29 W]] on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)
	# A w'''ritten report[[Written Report on View (Testing)]] on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.		# A w'''ritten report[[Written Report on View (Testing)]] on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.
	# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.		# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.

Kanke: /* Required Results */

2009-10-20T13:58:48Z

Required Results

← Older revision		Revision as of 13:58, 20 October 2009
Line 18:		Line 18:
	The following is required for your results:		The following is required for your results:
	# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).		# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).
	# A '''written report[~~[Written Report on Model (Testing)]~~] on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)		# A '''written report[http://pg-server.csc.ncsu.edu/mediawiki/index.php?title=Written_Report_on_Model_%28Testing%29 W] on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)
	# A w'''ritten report[[Written Report on View (Testing)]] on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.		# A w'''ritten report[[Written Report on View (Testing)]] on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.
	# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.		# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.

Kanke: /* Required Results */

2009-10-20T13:57:33Z

Required Results

← Older revision		Revision as of 13:57, 20 October 2009
Line 18:		Line 18:
	The following is required for your results:		The following is required for your results:
	# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).		# A '''.zip or .tgz archive''' containing the entire Buddi project (or at a minimum, all files which have changed OR a .diff of your changes, as you desire).
	# A '''written report[[Written Report on Model (Testing)] W] on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)		# A '''written report[[Written Report on Model (Testing)]] on the model testing''', indicating what your unit tests test (paying attention to edge cases where problems are more likely to occur) and the results of these tests. (The actual unit tests themselves will be included in the archive in part a)
	# A w'''ritten report[[Written Report on View (Testing)] W] on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.		# A w'''ritten report[[Written Report on View (Testing)]] on the view testing''', indicating what tests you performed, and what the results were. Screenshots taken throughout the test procedure are optional, but a very good idea to demonstrate what problems (if any) you have found.
	# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.		# '''A written report on what changes''' you have made to the view (or the model) as a result of your testing. If there were failures or potential improvements discovered in either your tests, this report should include a re-run of the failed tests, showing that they are now working.