On 6/17/2010 12:08 PM, Tommaso Teofili wrote: > 2010/6/17 Marshall Schor <[email protected]> > > >> >> On 6/17/2010 4:17 AM, Tommaso Teofili wrote: >> >>> Hi all, >>> as said previously OpenCalaisAnnotator and AlchemyAPIAnnotator are being >>> used inside (incubating) Apache Clerezza project to enrich graphs. >>> Yesterday an issue with OpenCalaisAnnotator came up, I made some quick >>> integration tests myself and verified that in some strange cases "begin" >>> >> and >> >>> "end" of some OC Annotations have both value '-7' resulting in >>> IndexOutOfBoundsException when calling annotation.getCoveredText() [1]. >>> For this reason I would like to put some unit and integration tests in >>> >> place >> >>> for the OpenCalaisAnnotator to check out and fix such an issue. >>> >>> >> Sounds good. >> >>> In order to debug OpenCalais annotations I'll have to generate (and >>> >> commit) >> >>> also TypeSystem classes. >>> >>> >> Why would this be an issue? Would these be test cases? Would this >> require some kind of "sign-up" for using the Open Calais services to run >> the test? (If so, could these be "mocked", instead?) >> >> > This shouldn't be an issue, only I was telling before doing it since, at the > moment, TypeSystem classes are not on SVN and I don't know if there was a > reason for that. >
My guess is that the type system classes change when Open Calais changes? But in any case, I don't see a problem doing this for testing, other than it may make the tests dependent on a particular version of Open Calais (assuming that it changes those types). -Marshall > For what concerns integration tests we can do mocked tests or like we do in > AlchemyAPI annotators tests: a mocked test and an actual integration test > supplying the runtime parameter required to make the webservice call. > Tommaso > >
