As all my testing teams are geographically distributed, I am obviously always trying to maximize the effectiveness of our test hardware infrastructure while looking very closely at costs (especially in this tough economic environment). I’m particularly trying to reach optimum flexibility and scalability for our environment. All the products I’m responsible for are developed and tested at different pace. They also might be at different maturity level requiring different test focus (I’m particularly thinking about performance and benchmarks). Continue reading
As we’re starting a new development under NetBeans, we have evaluated quite a bit of open source and commercial tools to cover all of our test requirement. This is the first time we undergo a software development under this development platform and we wanted to make sure we pick the right tools for the job. It was a good opportunity for us to go over some of the new tools available. Here are the tools we’re going to use:
We’ll use both tools to cover our lower level UI testing. They will basically be used whenever our UI funtional test tool (QFTest) can’t be used. Jelly will be used as the processing engine while Jemmy will be used to interact with the underlying UI at the Swing/AWT component level.