Some ideas to improve coverage support

[GoogleCodeExporter]

I have 3 ideas to improve apparat coverage tool:
1 - Add a metadata or interface to instrumented classes, to prevent classes to 
be instrumented twice and also allow to skip instrumentation (it may make sense 
in some scenarios)
2 - Skip empty constructors (or at least make that configurable), sometimes we 
just have classes that only contains static methods, so makes no sense to 
instrument this classes constructors
3 - Special handle quit functions like fscommand( "quit" ) and 
NativeApplication.nativeApplication.exit(). When this are encountered just 
consider it ran before invoking the actual code.  Once the real code is invoked 
the flash VM just quit and this lines look like not executed, although there 
were and they did close the flash VM.

Original issue reported on code.google.com by velo...@gmail.com on 14 Sep 2010 at 6:51

[GoogleCodeExporter]

Original comment by joaebert on 14 Sep 2010 at 6:55

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Also, apparat should skip interfaces.... make no sense instrument interfaces 
since they aren't executable at all.

VELO

Original comment by velo...@gmail.com on 21 Sep 2010 at 2:31

[GoogleCodeExporter]

its annoying but one could ignore a method if its (only) in a trait of an 
interface

Original comment by joaebert on 6 Oct 2010 at 10:23

[GoogleCodeExporter]

Moved to low priority since not many people use coverage.

Original comment by joaebert on 1 Feb 2011 at 8:11

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Not many people use coverage because it is currently hard to integrate 
(FlexMojos dependency on Maven for example is an adoption barrier). It has been 
a big need for every team developing Flex code. Any improvement in this area 
would be very well received.

Original comment by naa...@gmail.com on 5 Aug 2011 at 5:47

[GoogleCodeExporter]

Well, all this changes are for flexmojos =D

If you need a different platform you would need to implement it =D

Original comment by velo...@gmail.com on 5 Aug 2011 at 6:09

[GoogleCodeExporter]

By the way, I think I will add some changes to skip simply empty methods. This 
will fix the case for interface, empty ctor etc.

Also: if a method is empty it does not contain any logic, thus does not need to 
be covered anyways. Mostly those methods are generated by ASC.

Original comment by joaebert on 14 Oct 2011 at 10:42

[GoogleCodeExporter]

Original comment by joaebert on 14 Oct 2011 at 10:43