• Intro Headers Instructions Macros
  • Fork me on GitHub
    • Release
    • Introduction
    • How to install bnd
    • Guided Tour
    • Guided Tour Workspace & Projects
    • Concepts
    • Best practices
    • Build
    • Generating JARs
    • Versioning
    • Baselining
    • Service Components
    • Metatype
    • Contracts
    • Manifest Annotations
    • Resolving Dependencies
    • Launching
    • Testing
    • Packaging Applications
    • Wrapping Libraries to OSGi Bundles
    • From the command line
    • For Developers
    • Plugins
    • Tools bound to bnd
    • File Format
    • Header Reference
    • Instruction
    • Instruction Index
    • Macro Reference
    • Command Reference
    • Plugins Reference
    • Settings
    • Errors
    • Warnings
    • Frequently Asked Questions
    Supported by OSGi enRoute
  • -tester REPO-SPEC

    The -tester instruction defines what bundle is used to setup testing. This bundle must have a Tester-Plugin that will setup the test environment.

    By default the, -tester is the bundle biz.aQute.tester. This bundle will instruct bnd to add this bundle to the -runbundles, sets the appropriate properties, and then launches. It will then run whatever tests are configured.

    Older Versions

    For a long time bnd had biz.aQute.junit as the tester. This launcher added itself to the -runpath and then executed the tests from there. Unfortunately this required that the tester actually exported the JUnit packages. This caused constraints between JUnit and bnd that was not good because JUnit itself is not directly a shining example of software engineering :-(

    If you want to be backward compatible with the older model, set:

    -tester: biz.aQute.junit
    
    • Contact
    • Developers
    • More