<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" > <suite name="2016.1.0 Java SDK - 16.1 SSL p4d" verbose="1" > <groups> <run> <exclude name="project-server" /> </run> </groups> <test name="Standard"> <packages> <package name="com.perforce.hws.testing.p4base" /> <package name="com.perforce.hws.testing.server" /> <package name="com.perforce.hws.testing.server.project" /> </packages> <classes> <class name="com.perforce.hws.testing.Basic16_1SslEnvironmentTestSetup" /> </classes> </test> <listeners> <listener class-name="com.perforce.hws.testing.reporting.YamlReporter" /> </listeners> </suite>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#4 | 19615 | mphillips |
Reorder XML to Windows Eclipse TestNG likes the ordering. Trish has tried it out on Mac and it seems fine. |
||
#3 | 19535 | drobins | Refactor package names to hws | ||
#2 | 19338 | tjuricek |
Create custom reporting mechanism to allow for clear "multiple suite" reports... with logging! This standardizes on log4j 2 as the backend (was just used on the server side). We have an "in memory appender" that we use to capture results during testing, which we associate with each method run. The whole system spits out yaml files for each suite run, which are then read in via a final task and a single html report is spit out with ... everything... in it. |
||
#1 | 19277 | tjuricek |
Add self-signed SSL configuration variation (just with the 16.1 p4d) for testing. No bugs were actually uncovered, though it may be useful to debug environments. (If people don't have a properly patched JVM with the JCE extensions, this test will fail.) |