# Looking for Feedback on Automation Dashboard

**URL:** <https://club.ministryoftesting.com/t/looking-for-feedback-on-automation-dashboard/68505>\
**Category:** Discussions\
**Tags:** tools, automation, feedback\
**Created:** [14 June 2023 19:03 UTC](https://club.ministryoftesting.com/t/looking-for-feedback-on-automation-dashboard/68505 "2023-06-14T19:03:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![natebosscher](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/natebosscher/32/11937_2.png) [@natebosscher](https://club.ministryoftesting.com/u/natebosscher)\
**Post date:** [14 June 2023 19:03 UTC](https://club.ministryoftesting.com/t/looking-for-feedback-on-automation-dashboard/68505/1 "2023-06-14T19:03:22Z")

</div>

I’m looking for some feedback on my testing tool’s user interface. (am I missing something obvious? is it functional? am I communicating the value?)

My app self-drives around the customer’s web app and reports on UI and Functional errors and regressions. This thing is super powerful, I’m worried that I’m not communicating the depth of testing well enough. Any comments would be amazing (even ‘it sucks’ is helpful)

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/system/32/14378_2.png) [@system](https://club.ministryoftesting.com/u/system)\
**Post date:** [13 June 2025 19:03 UTC](https://club.ministryoftesting.com/t/looking-for-feedback-on-automation-dashboard/68505/2 "2025-06-13T19:03:40Z")

</div>

This topic was automatically closed after 730 days. New replies are no longer allowed.