Please refer to the mail I reply earlier to Tim. Here are more details.
The QL basically does the following:
1. Start up Derby.
2. Start up V3.
3. Build test APPs.
4. Create Users.
5. Deploy tests.
6. Compile test client.
7. Run tests and generate test report in quicklook/test-output-web
8. Undeploy test APPs.
9. Delete users.
10. Stop V3.
11. Stop Derby.
In Tim's case, if the QL build/testing process was forced to fail in the
middle of testing, the test results will be partial. I don't think the
QL tests should stop for tests failing in AMX alone. Also, V3 won't be
clean in that case. It would have testing APPs still deployed, testing
users left over, V3 and Derby process running. These are not ideal
testing scenarios for implementing automated QL Hudson job.
Please file issue/RFE in issue tracker if you still think this is a bug.
Thanks,
Ming
Sahoo wrote:
> Yes, it has been reported earlier, but there has been no action. I
> don't know what the author was thinking while writing the program...
>
> Tim Quinn wrote:
>> This has come up before, but I don't remember seeing any response or
>> action on it.
>>
>> Why does the last display of the QL test summary say it is successful
>> even if there were failures?
>>
>> - Tim
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>