ABOUT JAMO

Jamo Solutions provides state-of-the art solutions for UI-based test automation on mobile devices. 'Jamo Automator' is a codeless cloud-based  tool that lets you focus on the test case without the hassle of scripting.

GET IN TOUCH

Houtemstraat 157, 3300 Tienen, Belgium

© 2018 by Jamo Solutions

Jamo Automator - Browser based apps

Jamo Automator supports the automated testing of web sites on Chrome, Firefox and Edge browsers. The browser based app must be HTML based. The UI interface is recognised on a higher level. We do not talk about links, div objects. Instead, we denotes the UI objects as a list, a button, an image. By doing so, the automated test script becomes platform independent. The tester can replay the automated test case on other platforms like the browsers on a mobile device or against a mobile app as long as the user experience, including the navigation through the app is identical.

Why applying Jamo Automator instead of free-ware tools like Selenium?

Skills & learning curve:

  • The free-ware tools are code/programming based and require programming skills. The learning curve is high. It is difficult to include less technical people in the QA automation process.

  • Jamo Automator is a code-less environment. The test cases are easy to understand workflows. The learning curve to apply Jamo Automator is much lower. The workflow support all standard testing techniques: data driven testing, parameterisation, server access, verification point, etc.

Test case maintenance

  • The way to deal with changes in the UI is not guided by the free-ware tools. The experience of the QA engineer counts in coding test cases that are robust enough to deal with regression testing. Unfortunately in many cases, the UI engineer does not have a view on the planned changes nor an overview on the possible different data sets so that his scripts most likely fail in regression testing.

  • Jamo Automator includes an algorithm based replay engine with embedded AI techniques that ensures re-use of the test case across changes in the UI of the app under test. 

Note: Especially for Agile and DevOps one needs to reduce flaky tests to an absolute minimum. Flaky tests are tests that fail due to its implementation and not due to a bug in the app under test.