It's noted that on IDE, timely UI seems broken which results in poor user experience and frequent errors. To overcome these issues, there is a strong need for an automated test suite for the graphical editors part. These test suites will detect errors that will enhance the overall reliability of the editors. Through automated testing, we can effectively implement error indicators within graphical models, ensuring timely identification and resolution of issues.
This can be achieved by creating UI automated test suites which we are doing using SWTBot. With this issue, we are focusing mainly on type editors.
The whole UI testing for type editors has been divided into modules as below:
Hi @bwiesmayr,
Could you kindly add the "gsoc" and "ui-test" labels to all the following issues? Additionally, please assign these issues to me. This will help others to easily identify and track these issues.
It's noted that on IDE, timely UI seems broken which results in poor user experience and frequent errors. To overcome these issues, there is a strong need for an automated test suite for the graphical editors part. These test suites will detect errors that will enhance the overall reliability of the editors. Through automated testing, we can effectively implement error indicators within graphical models, ensuring timely identification and resolution of issues.
This can be achieved by creating UI automated test suites which we are doing using SWTBot. With this issue, we are focusing mainly on type editors. The whole UI testing for type editors has been divided into modules as below: