Simple Sanity Test to validate that all the bundles in a distribution are active... 14/1614/3
authorMoiz Raja <moraja@cisco.com>
Wed, 2 Oct 2013 17:43:54 +0000 (10:43 -0700)
committerGerrit Code Review <gerrit@opendaylight.org>
Wed, 2 Oct 2013 20:00:25 +0000 (20:00 +0000)
commit6a5de1746ad68b1fe9464ec414126f1b559737e2
treec4ff834e76f9aaa60b0ea03806921852ad6f491b
parent72f3cf2421324d9282addb7a880784b7ee05de0c
Simple Sanity Test to validate that all the bundles in a distribution are active and resolved

The idea behind the Sanity Test is to ultimately fail a build when the test fails. The test would
launch run.sh but with a slightly modified config.ini where the sanitytest bundle would be injected
as a framework bundle.

The test waits for 30 seconds for the container to finish loading all the bundles. It then gets all the
bundles from the BundleContext and checks if they are ACTIVE or RESOLVED. If they are neither it prints
out the name of the bundle and it's state and returns an error code.

Change-Id: Ia6905318f1cf63e852791ba107193094a83fddf1
Signed-off-by: Moiz Raja <moraja@cisco.com>
opendaylight/distribution/sanitytest/pom.xml [new file with mode: 0644]
opendaylight/distribution/sanitytest/src/main/java/org/opendaylight/controller/sanitytest/internal/Activator.java [new file with mode: 0644]