Could TeamCity be useful for us?
Hi,
Please ignore my ignorance: I have no clue, whether Team City could be useful for us. We are developing client side (Swing-based) applications with only a small amount of unit-tests, but a larger part of UI tests (Jemmy-based). Could Team City be of value for us?
Thanks in advance,
Tom
Please sign in to leave a comment.
Though we use abbot instead of jemmy we have a lot of Swing-GUI tests running under TC. No problems there.
I have to correct myself: no problems if your Swing-code does correct AWT-Event-Queue-Threading ;) ... Since TC runs the tests really often, bugs that are infrequently because of wrong threading will turn up quite fast.
Some teams had to fight hard confronted with all their subtle bugs that where finally shown, once their builds were run under TC.
Hello,
Does forking JVM for tests solves the issue? Or is the issue in the interference
of tests?
--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
If I understand the feature list correctly, TC is a tool which checks out our project periodically, builds it and runs its tests, right? Did I missed something important?
Tom
Oh, my yes.
The most important thing is that it can build and run your tests before you check in the code, and if you wish can be set to automatically trigger checkin if the build and tests succeed. It seems like a small difference, but in practice these feature ("Remote Run and Deferred Commit") save an enormous amount of time.
There's also a bunch of very nice reporting options, most especially in the TeamCity/IDEA integration. It makes it extremely easy for a dev manager to understand his team's progress and status, as far as actual builds committed goes.
--Dave Griffith
No - the issue is our code not (always) having proper synchronisation in multithreaded GUI-code.
These bugs would also turn up without TC (if someone would try as often and regularly as TC does ;) ).