<INTERNAL_LINK> (and the sub-pages) describes a more systematic approach for IDs and data-role attributes in the markup of A12 Widgets intended to be used for automated testing.
Once this concept is finished and approved, its implementation will
If you are interested in this approach and API, please have a look and comment here.
Is there any update on this? I would be also very interested in the reasons for choosing this tool, if other technologies have been considered and also why projects that have years of experience in ui testing a12 have not been consulted?
@milena-bright-crest and @dmueller_inactive: mgm has long year experience with QF-Test as a tool for Eclipse based app testing and is happy with the tool and esp. with QFS as the company behind it, because they supported us well. They now provide a tool also for Web App testing, and this triggered talks and ideas for collaboration. This triggered our activities here.
In the meanwhile QF-Test for Web has been evaluated by the A12 BPS/eQA team with the idea to use it for automating some of the manual eQA tests, but with the current state is was rather rejected.
Enhancing the IDs and data-role attributes on widget level has the potential to improve the integration in the tool - QFS could then adapt their “resolvers” to our widgets. This would improve the tooling and changes in the widgets could be adapted in the resolvers, which means that the widget changes would be transparent to actual tests.
This is a lower prio work stream, which we are still following up.
We do consult with the mgm customer projects - that is the purpose of my email and this Discourse thread.
Open tickets in this area are:
I would be very interested in the results of your inquiry, especially how other projects are testing A12 based software, what frameworks they use and what their overall experience is. Is there any wiki page where I could find that information?
From my project experience I would prefer a solution that is based on an open source framework that is supported by a larger community and is in general free to use for everyone instead of choosing proprietary software without a community but payed support plans. This way the tooling is available to all projects without having to take care of project budgeting.
In general I would love to have a solution where A12 provides modules for ui testing along with their product as building blocks for projects to use so that they can build up their ui tests with them. This way projects would not have to build and maintain those modules on their own but can rely on A12.