There's also the following configurations left in domain.xml after
running QL:
<config name="AMXConfigProxyTests.TEST"
dynamic-reconfiguration-enabled="false">
<property description="desc.for.prop0" name="prop0"
value="prop0-value" />
<property description="desc.for.prop1" name="prop1"
value="prop1-value" />
<property description="desc.for.prop2" name="prop2"
value="prop2-value" />
<property description="desc.for.prop3" name="prop3"
value="prop3-value" />
<property description="desc.for.prop4" name="prop4"
value="prop4-value" />
</config>
Ming Zhang wrote:
> Sreenivas Munnangi wrote:
>> Ming Zhang wrote:
>>> Jane,
>>>
>>> I have checked in one more test to delete http-listener "ls123452".
>>> Now admin tests can be run repeatedly without errors and the
>>> domain.xml gets cleaned up after each admin test run.
>>>
>>> Lloyd,
>>> the AMX tests still failed in the 2nd QL run
>> How many tests failed, if possible could you copy and paste the
>> failures from ql output.
>>> (iterateAllSanityCheck, testAMXComplianceMonitorFailureCount) after
>>> my change for admin tests. Is this due to the configuration changes
>>> in domain.xml after admin GUI loaded? Is it reasonable to expect AMX
>>> tests will accommodate the configurations of admin GUI in domain.xml?
>>>
>>> Thanks,
>>> Ming
> The runtestng.output is attached:
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net