- Print
- DarkLight
Autify NoCode Mobile Stability Plan
※ Please note that parts of this page are machine translated.
- This article contains information about features that were available before December 2023. This article contains information about beta features.
- This article contains information about beta features. We will continue to provide this functionality to those customers who are able to use it.
- Beta features are subject to change without notice.
Tap
Issues with tap assertions that we have provided
Until December 2023, Autify NoCode Mobile has provided tap assertion functionality using the following two methods of element identification.
- Page Source
- Identifies elements based on source code information.
- Machine Learning (ML)
- Machine Learning is used to analyze screenshots of the application and identify elements.
However, the following problems occurred and needed to be improved
- Incorrect elements may be selected in both page source and ML.
- Updating element information or changing the way elements are identified requires re-recording the scenario, which takes time to correct.
- When improving machine learning, it is difficult to prevent adverse effects on existing scenarios, making speedy release of improvements difficult (problems related to ML taps and ML assertions; see below).
To address these issues, Autify NoCode Mobile plans to release improvements to tap assertions.
Please refer to this page for information on the planned releases and future plans. (Some of these features have already been released.)
"Tap (Beta)" and "Quick Element Update
In January 2024, we launched Tap (Beta) and Quick Element Update features, which are new taps with a new element detection method.
Tap (Beta)" allows users to select elements with higher precision than before, and "Quick Element Update" allows users to update element information without re-recording when elements are missing due to changes in appearance.
In addition, XPath can be used to select an element in a way that is independent of its appearance, in cases where appearance is not suitable as a clue, such as when the appearance changes significantly.
Plans for future releases
Currently, "Tap (Beta)" and "Quick Element Update" require new recordings, but we plan to release a migration feature for existing scenarios in the future.
In addition, we plan to release a detailed configuration function for each step, which will enable stable element identification in cases where element identification was difficult with Tap (Beta).
We are also developing assertions to solve the same problems as with taps, and to make speedy improvements.
What to do in case of problems with taps and assertions
The issues we have been experiencing with the page source Machine Learning based tap assertions are as follows
In addition to "Tap (Beta)" and "Quick Element Update," we expect to resolve this issue by using the features we plan to release in the future.
Therefore, we ask that you try each of these features as described below.
- Tap-related issues
- Please try the new features ("Tap (Beta)" and "Quick Element Update").
- If you have any questions or problems persist in using the new features, please contact our chat support.
Until the release of the migration feature for existing scenarios, please use the "Tap (Beta)" feature by creating a new scenario.
If the new feature does not improve the situation, we expect to need more detailed configuration functions to identify the elements. Therefore, you may have to wait for the release.
- Inquiries about assertions
- We expect improvements with new features currently under development.
- Please try the new feature after its release and contact our chat support if the problem persists.
About chat support response
As in the past, you can still contact us about issues related to taps and assertions, but we will let you know when to try the new features as appropriate.
If the new features do not improve the situation, please contact us again.
If you have any other questions, please feel free to contact our support.