My first job was exactly that, selling windows app in Delphi. I joined the new team working on .net windows apps and we had an army of people clicking on UI all day long. They maintained their "test plan" on a custom software where they could report failures.

TBH, that was well done for what it was but really called for automation and lacked unit-testing.

I am forced to use a custom kv store for my current t project. That pos has a custom dsl, which can only be imported through a swing ui, by clicking five buttons. Also, the ui is for 1024 screens, they are tiny in my 4k monitor

I remember a test plan in a spreadsheet where no test had an ID.

I wish I could teach everything I learned the hard way at that job

To be clear this is a pretty modern company, not 10 years ago. CI/CD absolutely was a common best practice.