From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
'''Why run those tests?''' | '''Why run those tests?''' | ||
For example if those tests pass, bundles resolve for | For example if those tests pass, bundles resolve for all thermostat one-off-commands. For more details have a look at the AllStandaloneTests class in the sources. At least this should give some confidence that packaged thermostat isn't terribly broken. | ||
Revision as of 12:02, 24 September 2015
Getting sources
Upstream Thermostat source releases can be downloaded from: http://icedtea.wildebeest.org/download/thermostat/
Building standalone Integration Tests
$ wget http://icedtea.wildebeest.org/download/thermostat/thermostat-<VERSION>.tar.gz
$ tar -xzf thermostat-<VERSION>.tar.gz
$ cd thermostat-<VERSION>
$ mvn clean package
$ java -Dcom.redhat.thermostat.itest.thermostatHome=/usr/share/thermostat \
-Dcom.redhat.thermostat.itest.thermostatUserHome=$(mktemp -d thermostat.XXXXXXXXXX) \
-Dthermostat.agent.verbose=true
-cp $(ls integration-tests/standalone/target/thermostat-integration-tests-standalone-*.jar) \
com.redhat.thermostat.itest.standalone.ItestRunner
The last step runs very basic integration tests against packaged thermostat. A summary of the test run can be found in the "thermostat-itest-reports" folder, file "summary.txt". Should there have been failed tests, there should be one file per test class with details about the test failures in the "thermostat-itest-reports" folder.
Why run those tests?
For example if those tests pass, bundles resolve for all thermostat one-off-commands. For more details have a look at the AllStandaloneTests class in the sources. At least this should give some confidence that packaged thermostat isn't terribly broken.