<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="Debian Deployment" verbose="1">
<test name="Standard">
<packages>
<package name="com.perforce.hws.testing.deployment.deb" />
</packages>
<!-- Example of only running a single test -->
<!--<classes>-->
<!--<class name="com.perforce.hws.testing.deployment.deb.InvalidConfigTests">-->
<!--<methods>-->
<!--<include name="incorrectCharsetBreaksStatus"></include>-->
<!--</methods>-->
<!--</class>-->
<!--</classes>-->
</test>
<listeners>
<listener class-name="com.perforce.hws.testing.reporting.YamlReporter" />
</listeners>
</suite> | # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #3 | 19625 | tjuricek | Report a 500 for misconfigured P4CHARSET settings, make sure status reports an error, and make the log entry meaningful. | ||
| #2 | 19535 | drobins | Refactor package names to hws | ||
| #1 | 19380 | tjuricek |
Adjust post-install config to handle upgrades better, and a test for debian systems. - Our default config file has an invalid line to flag that the file has never been touched. It's removed on the first post-install config. - We guard against overwriting things the next times post-install config is run, like the keystore files. - There's a "media" setting in the install4j configuration to treat "never override" as config files, which avoid overwriting the config (finally found it), at least on debian. - Added a new test suite just to ensure the configuration file is not overwritten, only works for .debs at the moment |