Hi Jim,
> Your implementation also > raises an interesting design question about attaching invariant indexes > to sequences (as you do to index into the alignment scores matrix). > Well, it was the first option. But actually it may result to place unwanted constraints in future development. It could be easily replaced using the sequence ID in place of the sequence index (assuming that the method SequenceI#getName() is retuning the sequence ID, isn't it ?) What about this? > Thanks for taking the time to do this ! I also note that you have > bravely checked in a directory of JUnit tests! This has forced me to > think a bit about how to retrofit the legacy test data to this model. > Most of our test data sits in the examples directory, so that we can > get people to run import tests on their live Jalview installation if > they run into problems (this is a nice way of checking that their local > environment is good). Wonder if Groovy is the way to go here for a test > harness ? > > Jim. > Yes. In a recent project, I've started using Groovy + Spock (http://code.google.com/p/spock/) and it's really a perfect match, above all if there are data based tests, like you are arguing. I think it could be really a good choice for Jalview test harness. Best, Paolo _______________________________________________ Jalview-dev mailing list [email protected] http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
