When executing UI tests, such as SWTBot tests, when a test fails some popups might stay open and cause subsequent tests to fail. Even worse, the whole test suite execution can take longer than usual because all the following tests might fail after waiting for a timeout (of 5 seconds by default). It will also kill the visibility of the scope of impacted components.
To make sure you have UI tests that will evolve seamlessly with UI naming modification, use the Internationalized String and not the hardcoded value of text displayed in the UI. Even if hardcoding seems simpler at test writing time!
Here's how you can implement it with SWTBot and NLS.
This morning, the VM containing the master of our Hudson instance froze. I "powered it off" and then restarted...ah, Hudson restarted and the list of jobs appeared. No, oh no, not all the jobs! Some of them vanished. Noooooo...
Wait, don't panic, this blog post provides an explanation of how to raise Hudson jobs from their ashes!
I recently had the opportunity to see a presentation about NetBeans RCP given by Geertjan Wielenga at AlpesJUG, and to chat with the speaker afterwards. We had an interesting discussion about how NetBeans RCP and Eclipse RCP compare to each other.