search

mecano1 / vogar

Automatically exported from code.google.com/p/vogar
1 stars 0 forks source link

Detect test type at runtime #15

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently we use fallible heuristics like filename matching to decide how an 
action 
will be run (JUnit, jtreg, Caliper, or main). We should inspect the code using 
runtime reflection instead.

Original issue reported on code.google.com by jessewil...@google.com on 6 May 2010 at 8:36

GoogleCodeExporter commented 9 years ago 
But we need to know before runtime for classpath compilation reasons don't we? 
I'd 
still be happy with a --type junit or other similar flag. We could use our 
current 
heuristics to guess an appropriate value, but have a simple way to override it 
when it 
all goes wrong.

Original comment by b...@google.com on 6 May 2010 at 9:30

GoogleCodeExporter commented 9 years ago 
Our current compilation heuristic is, just compile with EVERYTHING on the 
classpath. It's 
crude, but it works.

Original comment by jessewil...@google.com on 6 May 2010 at 9:47

GoogleCodeExporter commented 9 years ago

Original comment by jsha...@google.com on 19 May 2010 at 12:39