Ramin Moazeni wrote:
I think the problem is in suites.All and the order in which the tests
are being executed...I wonder if the order really matters?

I think the order should not matter. The fact that it does must mean there is some problem with restoring the policy after some test changes it. It of course would be best to track that down instead of changing the order, but I don't have an issue with changing the order and filing a Jira issue for the problem.

Kathey



Reply via email to