FAQ
Harmony is different from all other codeless test automation tools. The locator problem is solved differently. The first step is to design the use cases. This is implementation-independent and should be done before coding. Based on the use case steps and the application the test cases can be created very fast and with few errors. By applying Harmony, you can make automated test cases for each sprint.
Operating system: Windows, Linux
Java SE Runtime Environment 8
Internet access
Google Chrome
harmony-runner.jar
Harmony is the only genuine test design automation tool. It involves use case test design technique. It means that you can make use cases from the requirements and Harmony generates abstract test cases that can be verified by the stakeholders. Harmony uses an extended Gherkin language (Gherkin++), by which you can write test steps very easily based on the use case steps. Thus you can make automated tests in every sprint. Harmony can use a stable locator that can be coded as a special attribute data-harmony-id.
There are two possibilities. The first is to insert data-harmony-id attributes into the code. Here is an example:
data-harmony-id={‘Project ‘ + project.title + ‘ ‘ + project.description}.
If we have a project Pizza with a description Use case testing, then the locator will be ’Project Pizza Use case testing’. This is a stable solution as for any change of the XPath expression, etc. this locator remains.
Another possibility is to use traditional XPath expressions. Even in this case, you can declare once in the Feature window such as: Sign in(I; “xpath://*[text()=’Sign in with Google’]”) and then you can use it as Sign in. If the expression changes, you should modify it only in one place.
Yes, Gherkin++ is very easy to learn as each test step contains a keyword, a category (parameter) then IS, and finally a choice (value) such as WHEN Login name IS Smith. You can create your test steps based on the use cases and the application. Most people could use it after one-two days.
A basic test design knowledge is necessary to write use cases. Using our user guide is usually enough. In some cases, you should get XPath expressions that are also very easy. On the other hand, category names are displayed when the application is running by the harmony runner.
Yes, you can. Harmony ‘s code is React code and we also use Harmony for testing Harmony.
Yes, you can.
Currently not, Harmony is a tool for functional testing.
Yes, if you created a project then you are the project owner and can permit others to edit or just read your project. Then more people can edit a project except for the same feature.
No, currently you should use Chrome.
Yes, you can. When tests are ready you can execute them in a CI environment, for example, you can use Jenkins.
Test data are separated from the test description within Harmony. Test data are described as ‘choices’. You can use abstract test data before implementation and later on you can extend with a concrete value, while the test description remains the original. However, you cannot use separate files, Excel sheets, etc.
You cannot maintain the original use case or test steps with other tools. When you stop using Harmony, you can get the generated test code and you can maintain it.
Yes, there is an on-premise version of Harmony, Please, contact us to learn more.