Issue #464 has been fixed for TestNG 6.12. However it seems that exactly the same problem occurs with the latest version 6.13
Issue #464 has been fixed for TestNG 6.12. However it seems that exactly the same problem occurs with the latest version 6.13