To enter and send text inputs to the Test Device:
Make sure the Editor is in mode.
Make sure the entry field on the Device Screen is active.
As an advanced user you can skip pressing
.
Just type in the text and press [Enter] to confirm and play the action.
For the last 14 years, I have been working on tools for developers at Thetaris. My Co-founder Stefan and I developed, we developed all kinds of tools, from Excel plugins, financial mathematics libraries, test suites, apps to a full-fledged IDE for our own programming language ThetaML. During this work, we found that many developers in our community struggle with maintaining their applications. The developers fix a bug or implement a new requirement and suddenly, a seemingly unrelated feature of the application breaks.
There should be an easy answer: testing. From the large projects we completed at Thetaris, we know that Unit-Tests are part of the solution. They are quick and can be used to automatically stop bugs from entering the code case. But they are not sufficient. The applications still break.
Manual testing is an expensive and time-consuming solution. However, it works. The testers identify not only functional issues, but also UX glitches and text typos. Consequently, testers need the focus of attention. The testers should be enabled to maintain their own automated tests. Over the years, we tried many different approaches to reach this goal.
I thought, why not make my testers to QA engineers. We created a Python library which uses a simple language such that test cases are easy to understand and easy to extend. In other projects we used Cucumber, a simple language to make test cases easy to understand. Both approaches delivered the same result: A QA engineer is required for the language definition and testers can run tests. In some cases, tester can add test themselves. But, usually, they need a developer again who changes some of the application code.
Why would that be? Why can testers not just test the software without knowledge of the internal workings? I thought that a manual tester uses the User Interface, only. This must be completely sufficient to write automated tests using the UI. Using my computer vision experiences, I created a prototype in Python to provide a proof of concept for a visual test automation. It worked surprisingly well. No inner knowledge of the application was necessary anymore.
Another main issue testers face when running automated tests is the constantly changing infrastructure: E.g. Google Chrome gets an update and the Selenium Driver breaks. The connection of the native app using Appium on the local desk is another constant source of issues. Working in the cloud with Browserstack for native devices and Mabl for websites shows that testing belongs in the cloud. Testers are more productive and happier when they do not have to care about the test system infrastructure.
The last missing piece to a wide acceptance of test tools by testers is simplicity. I am lucky that my Co-founder is a UX nerd. During the development of our own test platform, Stefan included iteration after iteration to minimize the required user interaction for test recording. Minimizing the decisions a user has to make, we are also minimizing errors the user can do. We constantly collect feedback from new users of our application and simplify it further.
Now, we have put it all together in the Testup project: Visual Testing using Computer Vision, Infrastructure in the Cloud and Simplicity by No-Code test creation. The effort is fruitful: Test are easy to create, easy to ready and easy to change. The next step is the version 0.9 which we will release in a few days with an open beta. We are looking forward to your feedback!
When you need to enter text into a text field that already contains a previous value, there is an efficient way. Schedule a click on the field, wipe with a SWIPE command from right to left and then use the BACK_SPACE key to remove the old value. After that, enter the new value.
Just press the key on Editor menu in Insert mode.
Just press the key on your keyboard.
Just click on the scrolling bar on the Device Screen and then play the action.
Just swipe by holding the mouse button down, where the swipe shall start and release the mouse button where the swipe ends. Click on “Play this” to perform the action on the system under test.
There’s a special page just about scrolling.
The anchor image cannot be found on the Device screen. This can mainly two reasons. Let’s go through them.
A common reason for the is that your website has changed. Thus, the image which we call anchor area cannot be found on the website. Make sure that your anchor area do not change. Animations or written date stamps are common pit falls. Here is a description how you should choose your anchor area. Now click on the red button and select “Retake image”.
Reset the system under test by choosing “Play to here“.
If the problem stays, you probably have Issue 1 and need to “Retake Image”.
In some cases, scheduling a click on a drop down menu entry will always select the first entry. In this case, you need to use the keyboard for selecting the proper entry:
Make the drop down menu active by scheduling a mouse click on it. Run the click.
Schedule <DOWN> until you reach the entry you need.
Schedule <ENTER> for selecting the entry.
If you are running testup.io in your production environment, the test execution will show up in Google Analytics. The best way to prevent this from happening is to create a filter for our IP address. Here is what you do:
Exclude Testup IP Address From Google Analytics
3.65.122.186
The testup.io app has a clear structure.
On the first hierarchical level you find the projects.
For every project you can define several test cases.
Everytime you run a test, TestUp automatically makes a recording. You’ll find them by clicking on the open-button on the testcase overview.
To inspect the recording in detail, you can click the view-button to see pictures of the recorded and run test.
After setting up new project you can see the empty testcase overview. As there is no test case recorded yet, the page is blank.
Advanced
If you like to learn basic actions in the Editor before creating your first real test case, leave all setting by default. This will take you to testup.io Playground.
After logging in to the testup.io app you see a blank project site.
That’s it. Your first project is set up. Now you can go on creating your fist test case.
