# Anatomy of test automation **URL:** \ **Category:** Archive\ **Tags:** automation\ **Created:** [1 February 2021 23:08 UTC](https://club.ministryoftesting.com/t/anatomy-of-test-automation/47048 "2021-02-01T23:08:46Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![anon68517856](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@anon68517856](https://club.ministryoftesting.com/u/anon68517856)\ **Post date:** [4 February 2021 04:04 UTC](https://club.ministryoftesting.com/t/anatomy-of-test-automation/47048/6 "2021-02-04T04:04:21Z")
In addition to what ben said, here are some things which one might expect from a no/low code tool > [@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/anatomy-of-test-automation/47048)._