Running SilkTest 6.5.1 w/ a Java App. I get these strange exceptions when running testcases.
Many look Silk related but I'm not sure. I just don't know if they are bugs in the application that Silk exposes or if there's some problem with Silk interacting with the app that causes the exceptions. Any thoughts?
at segue.monitor.AWTEventsListener.installListeners(Q apAWTMonitor.java:653)
at segue.monitor.QapSwingMonitor.addTableModelListene r(QapSwingMonitor.java:462)
at segue.javarecorder.RecEventListener.installListene rs(RecEventListener.java:622)
at segue.javarecorder.Recorder.startRecAction(Recorde r.java:126)
at java.awt.event.InvocationEvent.dispatch(Invocation Event.java:171)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 454)
at java.awt.EventDispatchThread.pumpOneEventForHierar chy(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForHierarch y(EventDispatchThread.java:151)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:145)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:137)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:100)
at com.nagrastar.toolkit.gui.table.ToolkitTableModel. removeTableModelListener(ToolkitTableMo
at segue.monitor.QapSwingMonitor$SwingEventListener.r emoveListeners(QapSwingMonitor.java:229
Originally posted by chuckles1856: ... What really sucks about this is how to explain to developers that there is a problem in their code when you have problems in your tools you use. Makes it hard for them to swallow.
<font size="2" face="Verdana, Arial, Helvetica">It won’t suck at all if you approach it differently.
Any experienced developer will acknowledge that every piece of software on the market has problems. After all, if the test tool developers had a lock on writing clean reliable code, the techniques they used to get there could be applied equally well to all other commercial software. They'd rule the software world.
As you've implied, it is embarrassing to submit a problem report that is rejected when the investigation points back to your process or the tool you used. You lose a little credibility when it happens just like the developers do when the situation is reversed. Expressing a superior attitude when the bug was initially reported only worsens the pain.
Take these situations in stride when they happen and learn from them. Software is a humbling business for everyone including testers who might think that their tools will make them invincible.
With experience you'll be a little more charitable to the developers the next time you challenge their creations with a bug report. By carefully testing your own work before you report a problem, the developers will come to respect your thoroughness and accuracy.
Regression -- That is interesting but rather unfortunate. What really sucks about this is how to explain to developers that there is a problem in their code when you have problems in your tools you use. Makes it hard for them to swallow.