From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
Upstream Thermostat source releases can be downloaded from: http://icedtea.wildebeest.org/download/thermostat/ | Upstream Thermostat source releases can be downloaded from: http://icedtea.wildebeest.org/download/thermostat/ | ||
= | = Getting and Running Standalone Integration Tests = | ||
$ wget <nowiki>http:// | $ wget -O thermostat-standalone-integration-tests-<VERSION>.jar <nowiki>http://builder.classpath.org/jenkins/job/Thermostat-1.4/lastSuccessfulBuild/artifact/integration-tests/standalone/target/thermostat-integration-tests-standalone-<VERSION>.jar</nowiki> | ||
$ java -Dcom.redhat.thermostat.itest.thermostatHome=/usr/share/thermostat \ | $ java -Dcom.redhat.thermostat.itest.thermostatHome=/usr/share/thermostat \ | ||
-Dcom.redhat.thermostat.itest.thermostatUserHome=$(mktemp -d thermostat.XXXXXXXXXX) \ | -Dcom.redhat.thermostat.itest.thermostatUserHome=$(mktemp -d thermostat.XXXXXXXXXX) \ | ||
-Dthermostat.agent.verbose=true | -Dthermostat.agent.verbose=true | ||
-cp $(ls | -cp $(ls thermostat-standalone-integration-tests-*.jar) \ | ||
com.redhat.thermostat.itest.standalone.ItestRunner | 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". | 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". In case of failed tests, there should be one file per failed test class in folder "thermostat-itest-reports". Look in those files for details about the test failures. | ||
'''Why run those tests?''' | '''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. | 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 upstream Thermostat sources. At least this should give some confidence that packaged thermostat isn't terribly broken. | ||
Revision as of 12:44, 21 December 2015
Getting sources
Upstream Thermostat source releases can be downloaded from: http://icedtea.wildebeest.org/download/thermostat/
Getting and Running Standalone Integration Tests
$ wget -O thermostat-standalone-integration-tests-<VERSION>.jar http://builder.classpath.org/jenkins/job/Thermostat-1.4/lastSuccessfulBuild/artifact/integration-tests/standalone/target/thermostat-integration-tests-standalone-<VERSION>.jar
$ java -Dcom.redhat.thermostat.itest.thermostatHome=/usr/share/thermostat \
-Dcom.redhat.thermostat.itest.thermostatUserHome=$(mktemp -d thermostat.XXXXXXXXXX) \
-Dthermostat.agent.verbose=true
-cp $(ls thermostat-standalone-integration-tests-*.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". In case of failed tests, there should be one file per failed test class in folder "thermostat-itest-reports". Look in those files for details about the test failures.
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 upstream Thermostat sources. At least this should give some confidence that packaged thermostat isn't terribly broken.