Hi all,
Some of the recently added ESB test cases caused 100 test failures when
executed on platform setup, the reason for failure was not using the custom
annotation properly. So you need to use appropriate annotations to skip
tests from certain test execution environments. The test framework can be
used to executes tests on two environments.
1. Stand-alone product - where test suites resides on the same machine with
product.
2. Distributed product platform - where framework and products are deployed
on distributed machines.
The framework has introduced @SetEnviroment annotation to skip tests from
certain test execution environments.
This is just to make aware of the usage of this annotation.
*Usage @SetEnviroment.*
1. When you make configuration changes to products by editing config files
(e.g axis2.xml, carbon.xml etc..)
2. When refer CARBON_HOME property inside test cases.
3. When copying class mediator etc to lib/dropins directory.
4. When you write tests by assuming test case will be run on local host
only.
e.g
*//test will be only executed at integration level*
*@Test(groups = "wso2.all", description = "verify server startup errors")*
*@SetEnvironment(executionEnvironments = {ExecutionEnvironment.
integration_all})*
* public void testVerifyLogs() throws RemoteException {*
*}*
Please talk to the QAA team if you need further clarification. We will add
this to the documentation.
Thanks,
Krishantha.
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
