The interface org.apache.maven.surefire.providerapi.SurefireProvider generally leaves it ut to the provider to determine what kind of object describes a test. Up until fairly recently, most of the providers used arbitrary strings, which *could* map 1:1 to a class, or could be something totally different, like a url. The implementation was changed by "someone" from string->class, for some reason I do not entirely remember; but the interface still leaves it up to the provider. Unless there has been some leaking in the abstractions, it should hold.
But it should (at least in theory) still be totally up to the provider; it returns a bunch of items in the "getSuites" method, and will receive each item in the iterator in the "invoke" item. Kristian 2013/10/21 Stephen Connolly <[email protected]>: > Kristian, > > I was looking to use Surefire to help running tests in scripting > languages... > > i.e. where the .class file is not necessarily created at all. > > I notice that Surefire's Providers API leans heavily on ScanResult which > seems to be biased towards assuming that there is a .class file for each > and every test. > > Is this something that you think could be easily unwound, or am I better > creating a separate test engine for non-class based tests > > -Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
