# Automated GUI testing with Ignition

**URL:** <https://forum.inductiveautomation.com/t/automated-gui-testing-with-ignition/15281>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [September 8, 2017, 10:41am UTC](https://forum.inductiveautomation.com/t/automated-gui-testing-with-ignition/15281 "2017-09-08T10:41:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JantjeBeton](https://avatars.discourse-cdn.com/v4/letter/j/ea666f/32.png) [@JantjeBeton](https://forum.inductiveautomation.com/u/JantjeBeton)\
**Post date:** [September 8, 2017, 10:41am UTC](https://forum.inductiveautomation.com/t/automated-gui-testing-with-ignition/15281/1 "2017-09-08T10:41:50Z")

</div>

Hi Everyone,

Has anybody got any experience with automated GUI testing on Ignition projects?  
What kind of tooling are you using? Pro’s and Con’s?  
We’re looking into it. Squish from Froglogic or basic (and free) Abbot…

Let me know!  
Martijn

---

<div class="post-metadata">

**Author:** ![dawei.liu](https://avatars.discourse-cdn.com/v4/letter/d/76d3ee/32.png) [@dawei.liu](https://forum.inductiveautomation.com/u/dawei.liu)\
**Post date:** [September 18, 2019, 5:01am UTC](https://forum.inductiveautomation.com/t/automated-gui-testing-with-ignition/15281/2 "2019-09-18T05:01:41Z")

</div>

@ JantjeBeton  
I have a similar situation as you. We also want to use a free opensource code to do GUI automated test.

Did you solve your issue?  
If yes, could you give some comments for the GUI automated test in your Ignition project?

I've searched in github that some open source tool such as pywinaumation, which support mouse and keyboard operation, but not sure it can catch the info of components such as the string or background color of a button in the HMI screen of Ignition.

BTW, I found a previous thread, it seems that IA uses the QF-Test, which is a commercial software.

> [@Automated user interface testing](http://forum.inductiveautomation.com/t/automated-user-interface-testing/4539):
>
> Has anyone tried an automated user interface test package with the Ignition client? A quick look has come up with packages like Marathon, Maveryx or Squish. We use Ignition as a front-end for a user’s database and it would be nice to test all the required functionality automatically before we install an update.

---

<div class="post-metadata">

**Author:** ![JantjeBeton](https://avatars.discourse-cdn.com/v4/letter/j/ea666f/32.png) [@JantjeBeton](https://forum.inductiveautomation.com/u/JantjeBeton)\
**Post date:** [September 20, 2019, 6:49am UTC](https://forum.inductiveautomation.com/t/automated-gui-testing-with-ignition/15281/3 "2019-09-20T06:49:49Z")

</div>

@dawei.liu  
We haven’t solved it in that way. We enlisted a student to program a custom GUI-test program.

---

<div class="post-metadata">

**Author:** ![Linda\_Garrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/linda_garrison/32/33166_2.png) [@Linda\_Garrison](https://forum.inductiveautomation.com/u/Linda_Garrison)\
**Post date:** [March 25, 2022, 9:20am UTC](https://forum.inductiveautomation.com/t/automated-gui-testing-with-ignition/15281/4 "2022-03-25T09:20:51Z")

</div>

QF-test is not bad, but after I tested my software by it, I needed to retest it from the start because it didn’t get me a whole pack of information, issues, etc. After it, I just gave my project to the right hands [https://u-tor.com/](https://u-tor.com/) and got a successful result. Testing is an essential part of developing any product, so I want to recommend you not to an economy on it and do testing during development, but not after it.