hope someone can help me with this... One of the added values of jfcunit is that it provides the ability to interact with the swing application using the swing event queue. I concluded that with this feature, I can create parallel tests. However, when I run multiple jfcunit test cases in parallel, in some case, at some random moment, the test fails. I think that the reason for this is because there is some intervention of the tests between each other: some windows receive focus, lose focus and this (I think) has an impact on the behaviour of the application. (By the way, I'm trying to test an application built by an external company). Is there a way to lock the event queue from other influences then the testcase? Is there another possibility? Thanks in advance.
regards,
Johan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a unsupported configuration. Swing can only handle a single input stream. When you are dealing with menu's the events comming into the components will most likely collide causing menus to be unposted before they are clicked.
You should not be running more than a single swing test at a time.
kevin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
hope someone can help me with this... One of the added values of jfcunit is that it provides the ability to interact with the swing application using the swing event queue. I concluded that with this feature, I can create parallel tests. However, when I run multiple jfcunit test cases in parallel, in some case, at some random moment, the test fails. I think that the reason for this is because there is some intervention of the tests between each other: some windows receive focus, lose focus and this (I think) has an impact on the behaviour of the application. (By the way, I'm trying to test an application built by an external company). Is there a way to lock the event queue from other influences then the testcase? Is there another possibility? Thanks in advance.
regards,
Johan
This is a unsupported configuration. Swing can only handle a single input stream. When you are dealing with menu's the events comming into the components will most likely collide causing menus to be unposted before they are clicked.
You should not be running more than a single swing test at a time.
kevin