Security is one of our top priorities and we are working according to strict security standards such as:
We are working with multiple companies with highly sensitive data such as banking and insurance and have gone through their strict security requirements.
We allow fully codeless solution so that any tester, without coding knowledge, can easily use it to automate her test scenarios. However, if you wish to add code, we allow that as well.
We are a SaaS solution, all is set up for you with a built-in framework. All you need to do is to define your test scenario, using a simple drag-and-drop canvas or design it during runtime using our on-the-fly test creation mechanism. It is as simple as a recording tool, only it creates a model, rather than a recording, which is more resilient to changes in the app and is easier to maintain, apply changes and reuse when needed.
We identify elements by multiple parameters in two ways:
A. Technical – by capturing multiple attributes such as id. This allows us to overcome changes in the app and refrain from breaking the test.
B.Contextual – By capturing text, position, size, etc.
We combine both ways into a scoring mechanism and that allows us to overcome when changes occur.
We identify elements in a semantic way. It is irrelevant to the system if it’s implemented by a button or a div. it will work both ways.
We automatically wait for 3 things:
A. Complete page load
B. All AJAX requests
C. All CSS animations
We will wait for a configurable amount of time (you can define it) and then it will throw the timeout error unless you define an explicit timeout when necessary.
You can easily set different data to different scenarios, for example, a login scenario is a fixed amount of steps but can be made with different emails and passwords – those are actually different data-sets. You can choose between entering manually or inject the values from an excel or a database.
A validation step is just another step in the scenario; you can have different types of validation as part of the scenario which can be done as part of the test.
You have the ability to stop upon failure or to continue to the next test; it is totally configurable.
Yes. Only mobile web at the moment rather than native apps, so all responsive functional testing for web applications are supported.
Yes, we do support React, Angular and other SPAs. We actually support any other web-based applications. We are agnostic to the language the app is written in.
It depends – if JavaFX was used to develop a web-based application – we support it. However, if it was used to develop desktop applications – we do not support it.
Yes, we would need to have access to the internal app through a local tunnel such as Whitelist, an IP, VPN, etc in order to do it.
We support web-based applications, we also allow adding backend validations using a specific agent installed on the server side and sync with the test.
We convert our model into Selenium scripts, not the other way around.
You can add multiple tests to a suite to define a specific scenario so it would run on different browsers and work environments.
Yes, we have an integration with Applitools which can be used to validate elements in a visual way.
Yes – if it’s a web app we can test it in different browsers and work environments, including mobile web.
It is all stored in the cloud so that any tester on your team can access the test elements and reuse them.
We are a full SaaS solution and all tests are stored in the cloud. However, you can download the scripts after they are created and then archive them on-prem.
It exists in the settings of the Project.
TestCraft is a test automation tool, which is based on Selenium open source code. It has many different advantages over using Selenium and is making Selenium accessible to any tester, not only to those that can code. Unlike Selenium, it is completely SaaS, fully codeless, much less fragile, easy to use and easier to maintain over time. The visual way in which TestCraft works makes it much easier to design and maintain the tests and to reuse elements, which makes it a lot faster than using Selenium.
You can use the auto identification, or you can do it manually, both methods are applicable.
You can define and test hidden elements.
Yes, you can trigger that in a scheduled manner, through CI/CD. We are integrated with all leading CI/CD platforms, such as Jenkins, TeamCity etc.
It is highly reliable. You can even edit it manually if needed and if it breaks the fix only takes a second and can be done using our On-the-Fly mechanism during runtime.
Yes, both are available.