Test automation solution, handcrafted for Eclipse with revolutionary state management, ubiquitous language, modern IDE, and Maven/Tycho plugins.
End-user and product analytics solution that gives you rich insights into your application health, performance, and usage patterns.
Full-featured Integrated Development Environment for emerging Fantom programming language.
Xored originated as an Eclipse-centric company and since the year of 2002 we have delivered dozens of applications based on Eclipse Platform and Technologies. This is a broad set of applications and areas of experience: open-source technologies, commercial products, in-house tools, IDEs and modeling tools, as well as different types of customers, including software engineers, start-ups, and leading
enterprises. We believe that we have an exhaustive knowledge of application development lifecycle and how to deliver Eclipse-based solutions.
However, even though we had succeeded in delivering products from ground up, one thing was hindering our delivery process: test automation. Eclipse Ecosystem is full of useful technologies, tools, and expertise, however, it lacks a strong base to support QA processes. We came a long way trying to find a testing instrument for our solutions and adopt
different tools and technologies available on the market in order to automate our functional and UI tests. Test automation is essential to our agile development process and continuous product delivery, yet none of existing solutions was able to bring us to necessary level of agility. Thus we decided to put our Eclipse expertise into the best Functional and UI testing platform for Eclipse applications we can imagine and created Q7.
Q7 is a product Handcrafted for Eclipse. It was initially designed to help with automated testing of Eclipse-based applications and we had never considered expanding to any other technologies/platforms. There are lots of tools, which are fairly good when it comes to a variety of technologies but proved to be inconvenient or plain useless when it comes to Eclipse. The reason is quite obvious: while trying to cover as many platforms
as possible and expand to all available markets, their vendors have to get down to one basic and very common approach to rule them all and/or spend tons of resources in order to improve technology-specific features.
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:
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.