Skip to end of metadata
Go to start of metadata

Q7 next generation Eclipse Testing Tool

As a tool handcrafted for Eclipse, Q7 understands Eclipse application internals and integrates closely with Eclipse Technologies, going beyond UI testing and providing out of the box support for Eclipse Platform, SWT/JFace, IDE, GEF/GMF, and others.



The majority of UI testing tools are able to perform solely at the UI level. These tools are communicating with the Application-Under-Test by means of UI elements as most of its users would do.


Q7 acts in a completely different way. Its first essential distinction lies in Code Instrumentation. Q7 instruments the code of your Application-Under-Test so that it can monitor the internal events of the application and the Eclipse Platform. Moreover, Q7 injects its own code, allowing us to control the application and bring it to
a certain state, which is a key feature for running test cases.


This approach has significant advantages, which let us make Q7 so unique among other tools, such as:


  • We can avoid using Wait operations in our test case code: while your QA engineers have to spend an enormous amount of time putting delays between UI operations and/or writing supportive code to wait for the operation to be completed, Q7 knows a lot about what’s happening inside your application and uses this knowledge to understand when operation is completed.
  • Platform independence: Q7 is fully operating/windowing system independent. Tests created on Windows can be immediately replayed on OS X, and ready to be run on Linux within your Continuous Integration environment.




As a small software company, which is constantly hunting for the best engineers around, we cannot afford any productivity loss as well as engagement of valuable software engineers in tasks that can be done without significant experience of software development and very likely without a good knowledge of programming languages.


When it comes to testing, many companies employ non-programming staff for manual testing work. Our goal was to let your existing staff move on to automation of functional tests, enabling every QA engineer from this pool to deliver dozens or hundreds of test cases per month and cover all functional testing needs of a SCRUM Team alone.