testng-javascript-16.1.xml #5

<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="2016.1.0 Javascript SDK - p4d 16.1" verbose="1" >
    <groups>
        <run>
            <exclude name="project-server" />
        </run>
    </groups>
    <test name="Standard">
        <classes>
            <class name="com.perforce.hws.testing.BasicJavascriptEnvironmentTestSetup" />
            <class name="com.perforce.hws.testing.JavascriptTestFactory" />
        </classes>
    </test>
    <listeners>
        <listener class-name="com.perforce.hws.testing.reporting.YamlReporter" />
    </listeners>
</suite>

#	Change	User	Description
#5	19615	mphillips	Reorder XML to Windows Eclipse TestNG likes the ordering. Trish has tried it out on Mac and it seems fine.
#4	19535	drobins	Refactor package names to hws
#3	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.
#2	19174	tjuricek	JaCoCo code coverage setup and test cleanup revisions. During test cleanup we remove the directory the code coverage data is written to, so we need refined control on where the output file goes (which is copied to a build directory, currently).
#1	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.