aricdkwest.blogspot.com
Aric D K West: September 2008
http://aricdkwest.blogspot.com/2008_09_01_archive.html
Aric D K West. Thursday, September 25, 2008. Coverage testing with Emma. Among the tools I downloaded and set up while working on my stack testing. Links to the files I talk about in this post can be found there) is one called EMMA. It is a coverage tool which goes together with JUnit testing and reports to the user how much of the overall code was actually seen by the test cases. Here is a part of the sample output from EMMA:. From there I started to improve on the TestClearStack class. One of the f...
dmarakaki.blogspot.com
Daniel's ICS 413/414 Engineering Blog: November 2008
http://dmarakaki.blogspot.com/2008_11_01_archive.html
Daniel's ICS 413/414 Engineering Blog. Tuesday, November 25, 2008. DueDates: Part Deux Point Zero. Reformulate DueDates 1.2 into a working web application using Wicket. The team was able to meet all benchmarks of the system including an extra credit assignment which required DueDates 2.0 access more libraries. For DueDates 2.0. Team Akala is made up of Arthur Shum. Note: Because Arthur reorganized the package structure of DueDates 2.0, he will have a high number of commits on 12/7/2008. The chart below r...
dmarakaki.blogspot.com
Daniel's ICS 413/414 Engineering Blog: Code review: The Good, The Bad, The Ugly
http://dmarakaki.blogspot.com/2008/10/code-review-good-bad-ugly.html
Daniel's ICS 413/414 Engineering Blog. Wednesday, October 22, 2008. Code review: The Good, The Bad, The Ugly. First off I needed to come up with clever title for the blog and I thought The Good, the Bad, and the Ugly was appropriate for reviewing code. I would like to mention that in no way is the title a reflection of my fellow classmates' programs. I will however, point out what I thought was specifically good, what was generally bad, and make a general statement about what was ugly. For (int i = 1; i.
danielftian.blogspot.com
Engineering Blog (temporary title): December 2008
http://danielftian.blogspot.com/2008_12_01_archive.html
Engineering Blog (temporary title). Monday, December 8, 2008. Final showdown: DueDates 2.0 vs. Akala Group. It's time we ended this. Finally, it's come time for DueDates 2.0, the final battle in our quest for programming glory. It was a tough beast indeed, requiring us to conquer both XML parsing and Wicket. Webapp coding. Though we suffered some bruises, in the end we dominated the monumental challenge put ahead of us! Could do into a webapp, we also had to add in XML parsing using JAXB. My role was to ...
danmarakaki.blogspot.com
ICS 413/414 Software Engineering blog: November 2008
http://danmarakaki.blogspot.com/2008_11_01_archive.html
ICS 413/414 Software Engineering blog. Tuesday, November 25, 2008. DueDates: Part Deux Point Zero. Reformulate DueDates 1.2 into a working web application using Wicket. The team was able to meet all benchmarks of the system including an extra credit assignment which required DueDates 2.0 access more libraries. For DueDates 2.0. Team Akala is made up of Arthur Shum. Note: Because Arthur reorganized the package structure of DueDates 2.0, he will have a high number of commits on 12/7/2008. The chart below r...
dmarakaki.blogspot.com
Daniel's ICS 413/414 Engineering Blog: DueDates: Part Deux Point Zero
http://dmarakaki.blogspot.com/2008/11/duedates-part-deux-point-zero.html
Daniel's ICS 413/414 Engineering Blog. Tuesday, November 25, 2008. DueDates: Part Deux Point Zero. Reformulate DueDates 1.2 into a working web application using Wicket. The team was able to meet all benchmarks of the system including an extra credit assignment which required DueDates 2.0 access more libraries. For DueDates 2.0. Team Akala is made up of Arthur Shum. Note: Because Arthur reorganized the package structure of DueDates 2.0, he will have a high number of commits on 12/7/2008. The chart below r...
danmarakaki.blogspot.com
ICS 413/414 Software Engineering blog: October 2008
http://danmarakaki.blogspot.com/2008_10_01_archive.html
ICS 413/414 Software Engineering blog. Thursday, October 30, 2008. Code review: Learning from others. DueDates version 1.1. Gets reviewed by the other development teams in class. Team Purple was assigned to review Team Blue's DueDates. And assess their version 1.1 code and documentation. The class, also was assigned to evaluate Google Project Hosting's code review tool because of issues from the previous Code Review. Due dates. The comparator is defined as an anonymous nested class. Were not too critical...
danielftian.blogspot.com
Engineering Blog (temporary title): Final showdown: DueDates 2.0 vs. Akala Group
http://danielftian.blogspot.com/2008/12/final-showdown-duedates-20-vs-akala.html
Engineering Blog (temporary title). Monday, December 8, 2008. Final showdown: DueDates 2.0 vs. Akala Group. It's time we ended this. Finally, it's come time for DueDates 2.0, the final battle in our quest for programming glory. It was a tough beast indeed, requiring us to conquer both XML parsing and Wicket. Webapp coding. Though we suffered some bruises, in the end we dominated the monumental challenge put ahead of us! Could do into a webapp, we also had to add in XML parsing using JAXB. My role was to ...
dmarakaki.blogspot.com
Daniel's ICS 413/414 Engineering Blog: October 2008
http://dmarakaki.blogspot.com/2008_10_01_archive.html
Daniel's ICS 413/414 Engineering Blog. Thursday, October 30, 2008. Code review: Learning from others. DueDates version 1.1. Gets reviewed by the other development teams in class. Team Purple was assigned to review Team Blue's DueDates. And assess their version 1.1 code and documentation. The class, also was assigned to evaluate Google Project Hosting's code review tool because of issues from the previous Code Review. Due dates. The comparator is defined as an anonymous nested class. Were not too critical...
dmarakaki.blogspot.com
Daniel's ICS 413/414 Engineering Blog: Code review: Learning from others
http://dmarakaki.blogspot.com/2008/10/code-review-learning-from-others.html
Daniel's ICS 413/414 Engineering Blog. Thursday, October 30, 2008. Code review: Learning from others. DueDates version 1.1. Gets reviewed by the other development teams in class. Team Purple was assigned to review Team Blue's DueDates. And assess their version 1.1 code and documentation. The class, also was assigned to evaluate Google Project Hosting's code review tool because of issues from the previous Code Review. Due dates. The comparator is defined as an anonymous nested class. Were not too critical...