testng-basic-15.1.xml #6

<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="2016.1.0 Java SDK - 15.1 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.Basic15_1EnvironmentTestSetup" />
        </classes>
    </test>
    <listeners>
        <listener class-name="com.perforce.hws.testing.reporting.YamlReporter" />
    </listeners>
</suite>

#	Change	User	Description
#6	19615	mphillips	Reorder XML to Windows Eclipse TestNG likes the ordering. Trish has tried it out on Mac and it seems fine.
#5	19535	drobins	Refactor package names to hws
#4	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.
#3	19053	tjuricek	Rebuild JavaScript Client SDK. The JavaScript client now is a "typed" approach that tends to be similar in approach to the other clients, based on the swagger definition for the platform version. Importantly, client SDK tests are individual scripts (that run under node) that are actually controlled via TestNG. This approach now lets us use a consistent test reporting format so we can at least collect reports from each of the jobs. The documentation is still in progress, that I want to validate as the tests are generated.
#2	19020	tjuricek	Setup the deployment changes for multi-server configuration and JWT token setup. Note: we don't setup our installation to operate as a Helix Sync "project server" by default, so we don't run those tests at the moment. (What a project server actually will be remains to be seen, actually.)
#1	18846	tjuricek	Added test setups for p4d versions going back to r14.1. There is now a big single testng test suite that runs through most of these variations. I've switched to using the p16.1 builds by default, which can easily be switched to the r16.1 builds. Mainline p4d builds are still in use, since they are informative. We may want to not use those on candidate line runs, however.