Expanded Code Tests WishList

As requested, this is the updated Code Test Wishlist as of 12/7/12

High Priority

1. A way to filter out code that is disabled.
1. I tried using expressionStatement.isEnabled() but got TypeError: 'edu.cmu.cs.dennisc.property.BooleanProperty' object is not callable
2. A way to check whether or not a user method is called in myFirstMethod().
1. My tests give false positive when a passing construct is in a userMethod that is never called.
3. A way to isolate the code from Scene Setup.
1. This is potentially related to the previous wish.
2. Besides being useful for the tests I write for the Scene Setup badge, I think distinguishing between UserMethods, myFirstMethod() and Scene Setup will also be helpful for the mentors writing code tests. Although I know that scene setup behaves like any other code the user writes, that is not apparent to someone who doesn’t know the guts of Looking Glass since the IDE keeps the two separate.
4. A way to check and see if the code comes from a remix.
1. This is important if I want to distinguish between a remix a full badge
5. An isValid() boolean for each AOB. -> would be nice to save out the tests so that I can call/use them in other tests \
1. I think these would have to somehow have access to other code (?) because it would want to check any userMethods that were called in it)

Not terribly urgent

1. A way to see what actions the user has taken while making their world. (This would be things like playing the world, or zooming out during a remix. Although these were skills when Caitlin and I were first thinking about badges, I know that the test for these may be hard to implement, and we may need to restructure the criteria for these).
2. A larger window for the output in the IDE, or at least the ability to expand it