The release notes for Q7 version's located here – Release notes and Version Changelog
Browse this space for pages related to various help topics. Also we have a bunch of screencasts here – http://www.xored.com/products/q7/q7-demos/
Just drop us a line at firstname.lastname@example.org. Also we have a public Jira here – http://jira4.xored.com.
Please use these direct links:
See the detailed steps here – Configure Environment for AUT
See steps here - Locate Workspace for AUT executed from Q7
There are two ways to launch Q7 tests in continuous integration environment:
Both produce JUnit reports, which can be understood by continuous integration servers like Bamboo or Jenkins/Hudson.
Right now there's no way to set test execution order explicitly, because we are trying to keep Q7 tests independent. Thus, instead of having one test to reuse an environment prepared by another, we use state management, more on this is described on this page – http://www.xored.com/products/q7/q7-discover/state-management/.
Both Q7 Runner and Q7 Maven Plugin can 'install' your plugins before test execution into an existing Eclipse application, for example into existing Eclipse package downloaded from eclipse.org, see injection.
It is easy, just begin recording for your GEF/GMF diagram.
Q7 is mainly targeted to Eclipse SWT/RCP application testing. We have basic support for browser embedded into Eclipse, but with a lot of limitations.
We have technology preview of RAP based applications support, but it is not yet ready for production. Please check to Connect Q7 to RAP application from sources for more information.
Standalone browser applications are not planned to be supported.
ECL stands for Eclipse Command Language – it is open-source general-purpose scripting language which is used by Q7.
Please take a look here – http://www.xored.com/products/q7/q7-discover/eclipse-command-language/
Syntax is described in ECL wiki on Github – http://github.com/xored/ecl/wiki/Syntax
The API for the actual version (latest available at http://www.xored.com/products/q7/q7-downloads/) can be found at http://download.xored.com/q7/docs/ecl-api/latest.
See the New Command Guide
Basically all you need is to make sure that the plugin defining your commands is present in your application under test. To avoid putting extra plugins to your product during continuous integration, we recommend to use injections. An illustration of the whole process can be found in this GitHub repository – http://github.com/xored/q7.extensions.ecl.