testControlByteCode

History and use case

Since 2011

Tool created after multiple runtime problem.

Use case :

• Identify missing libraries on runtime
• Identify duplicate files in the classpath
• Check if all methods called in application are present in the dependencies with the right signatures
  • Example : public void method1(String arg1, String arg2) become public void method1(String... args)
• Dependency analysis between libraries
• Creates a graphviz file (.dot) to display dependencies via a graph
• Determines or controls dependencies of a library

Running the tool

• Add the maven/gradle dependencies in your project test scope

<dependency>
    <groupId>com.efluid.oss</groupId>
    <artifactId>test-control-byte-code</artifactId>
    <version>1.2.0</version>
    <scope>test</scope>
</dependency>

• Create new Junit test who just extending (see the examples here https://github.com/efluid/testControlByteCode/tree/master/src/test/java/com/efluid/example)

  • TestControleByteCode
  • TestControleFichiersEnDoublon
  • TestDependenceJar
  • TestAPIsDependenceJar

• Add yaml configuration in src/test/resources like this examples : https://github.com/efluid/testControlByteCode/tree/master/src/test/resources

• Run Junit tests