# Share your biggest frustration with testing tools – 30 Days of Tools, Day 16 **URL:** \ **Category:** 30 Days of Testing\ **Tags:** tools, 30-days-of-tools\ **Created:** [15 October 2021 19:00 UTC](https://club.ministryoftesting.com/t/share-your-biggest-frustration-with-testing-tools-30-days-of-tools-day-16/53426 "2021-10-15T19:00:10Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![anon68517856](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@anon68517856](https://club.ministryoftesting.com/u/anon68517856)\ **Post date:** [31 October 2021 22:56 UTC](https://club.ministryoftesting.com/t/share-your-biggest-frustration-with-testing-tools-30-days-of-tools-day-16/53426/9 "2021-10-31T22:56:13Z")
My biggest frustration is with low/no code testing tools. They take away flexibility, don’t have proper debuggers, their “code”/output is hard to reuse;version;refactor etc. I prefer to avoid them as mentioned in my posts below. The clueless management types seem to like them very much, especially after they get dazzled by the slick marketing teams of such tools. > [@Codeless test automation tool](https://club.ministryoftesting.com/t/codeless-test-automation-tool/45501/3): > > TL;DR - I avoid codeless tools if I can. But, I might be open to using them if my needs will never change significantly. I have used two codeless automation tools, one for non-testing work & another for testing work. I have seen short demos of some more. I noticed that such tools are essentially a UI layer over code/frameworks. Ex. Functions can become drag & drop widgets with text fields for inputs & output fields. Custom code can be another widget which opens up a code editor etc. Ex. SoapUI … > [@New codeless automation tool](https://club.ministryoftesting.com/t/new-codeless-automation-tool/46832/2): > > Here are some questions. 1 - Does it allow us to code in case we need custom functionality also? If yes, then which programming languages does it support. If no, then is it in your roadmap? 2 - Does it allow us to debug tests, i.e. run them step by step? Are there any limitations in your debugger like needs too much memory, can be used only for certain parts of the test cases and not the entire test case etc. Can we inspect any variables if we need to during debugging? 3 - Code or no code,… --- _[View the full topic](https://club.ministryoftesting.com/t/share-your-biggest-frustration-with-testing-tools-30-days-of-tools-day-16/53426)._