On Aug 4, 2008, at 4:49 PM, Adam Heath wrote:
Jacopo Cappellato wrote:On Aug 4, 2008, at 4:18 PM, Adam Heath wrote:I agree it would be great to have more and more automated tests; however some of the ones that we already have were failing due to the casting error in the "iterate" operation... I guess you didn't run them :-)Jacopo Cappellato wrote:yeah,I am getting (and I have reported a few hours ago) a similar error when receiving items into inventory. Adam, did you get a chance to test the applications using the framework components you have modified? If they are working for you, then you may have missed to commit a part of your work.I did test, but obviously not everything. It's not possible for a human to test every single bit of the code; that's why we need more automated tests.You're right, I didn't. Sorry.
No need to apologize, you are doing a big amount of code changes and issues like this can rather easily be introduced.
Running tests at the top-level, for the entire container, can be painful when one is working on an isolated level. It needs to be simple to run a tests in smaller chunks.
I know there is a way to run the tests on a single component, I don't remember the syntax, but it should be rather easy to find somewhere (Confluence or ML).
On that note, I'm going to start working on junit tests for individual bits of code; minilang will be the first one that I do. I'll get the basic stuff started, then it should be easy for others to see how I'm doing it, and help out with it.
More automatic tests on framework component are welcome (as the ones on application level components)!
Jacopo
smime.p7s
Description: S/MIME cryptographic signature
