Automated Tests on JNAerated results : "compilability" of interfaces and presence of expected symbols

hzzc1987 / jnaerator

Automatically exported from code.google.com/p/jnaerator

0 stars 0 forks source link

Automated Tests on JNAerated results : "compilability" of interfaces and presence of expected symbols #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

We need to test that code based on JNAerated sources will keep on building 
with forecoming changes.

We could use the Java Compiler API + a set of C headers + associated Java 
files that refer to predefined library names that would be generated.

Original issue reported on code.google.com by olivier.chafik@gmail.com on 18 Feb 2009 at 10:31

GoogleCodeExporter commented 8 years ago

Original comment by olivier.chafik@gmail.com on 19 Feb 2009 at 10:09

Added labels: Test

GoogleCodeExporter commented 8 years ago

Original comment by olivier.chafik@gmail.com on 19 Feb 2009 at 10:10

Added labels: Tests
Removed labels: Test

GoogleCodeExporter commented 8 years ago

It is crucial to get these automated tests running.

Original comment by olivier.chafik@gmail.com on 19 Feb 2009 at 10:15

Added labels: Priority-High
Removed labels: Priority-Medium

GoogleCodeExporter commented 8 years ago

Original comment by olivier.chafik@gmail.com on 21 Feb 2009 at 9:57

Added labels: Component-Tests
Removed labels: Tests

GoogleCodeExporter commented 8 years ago

Original comment by olivier.chafik@gmail.com on 25 Mar 2009 at 9:11

Changed state: Fixed