Armware
Posted By shanmoon on February 17, 2012
Armware
My left arm hardware (sans the ‘lag’ screws that could not be safely removed). I wonder what this much surgical grade titanium is worth…
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| « Feb | ||||||
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 | |||
-
.: Gallery Preview :.
.: Search :.
Addicted to Learning?
Posted By shanmoon on November 6, 2011
Aeronautics
I’ve come to realize, that I greatly enjoy the act of learning and gaining knowledge. So, I’ve enrolled in a couple of graduate classes in Aeronautics, just because I find it to be a fascinating subject.
Talk like ye be a pirate!
Posted By shanmoon on September 19, 2011
Arrr, ye scruvy dogs! It be International Talk Like a Pirate Day. Today only me ol’ blog will be readin’ most piratey!
Harvard Graduation
Posted By shanmoon on May 29, 2011
Harvard - May 2011
2011 Soaring Season Begins
Posted By shanmoon on February 26, 2011
2011-02-26 Flight Path
Flight Track from Flght Recorder: (more…)
JUnit4 Annotations and Ant Workaround
Posted By shanmoon on February 10, 2011
I usually use Maven for Java based projects, so my ant skills are a little rusty. Recently It was whipping up some JUnit negative test cases for someone else’s project that was a mess of ant build files (ugh). I decided to use some of the nifty annotation features found in JUnit 4.8.2 ( for rules and expected exception behavior). Annotations are great for addressing defects in the Java language, and help encapsulation by associating behavior directly with a class. But I digress… Anyway All the tests to check exceptions were thrown under negative test conditions looked good inside of Eclipse, but when I ran the ant test script from the command line, none of tests were being run encfprcomg the annotations, even though the JUnit jar was in the ant classpath! A little research showed that ant’s JUnit test runner doesn’t support annotations. The solution was to modify the suite() method of the AllTests class to wrap the classes under test in a JUnit4TestAdapter, i.e. something like this:
@RunWith(JUnit4.class)
public class AllTests extends TestSuite {
public static junit.framework.Test suite() {
return new JUnit4TestAdapter(TestSomething.class);
}
}