[hbsbsbsndk]

I worked on a product where there was basically no automated testing, just a huge product surface to click around with a bunch of options. Because of technical debt some of the options would trigger different code paths, but it was up to the developer to memorize all the code paths and test accordingly.

After I shipped a bug the Director of Engineering told me I should "test better" (by clicking around the app). This was about 1 step away from "just don't write bugs" IMO.

[stevage]

Yep, my first job was at a company like that. Huge Windows desktop app built in Delphi. No automated testing of any kind. No testing scripts either. Just a lot of clicking around.

[cryptonym]

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.

[HdS84]

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

[01HNNWZ0MV43FF]

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

[hbsbsbsndk]

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