I currently do not, and I am in general in the advocate against them group. Not because there is no place for test cases, but because they typically are used to serve a lot of different needs. And as with all things when you try to do to many things at the same time you tend to do none of them well.
Common things people try to use test cases for.
Test Design - Thinking about what needs to be tested and this is the documentation from that work.
Test Distribution - A team of testers want to test the same product so they need to share that problem.
Onboarding / Knowledge Transfer - A new member joins I you want to provide some information about the product and testing.
Status Reporting - Where are we with the testing effort.
Test Reporting - What did you test.
Test Instructions - What should you actually do to test a specific thing.
Test Automation Requirements - This is what you should automate.
A quick note on the difference between the test design (the intent of the test) and the test instructions (the steps needed to perform the test) is a commonly overlooked distinction.
Early in my career when exclusively, extensively and rigorously using test cases I had an observation that the best testers around me had a tendency to find bug outside of the test cases. That is, if I performed the test cases and they performed the test case I did not find the bug but they did. And the obvious explanation is that they did something outside of the documented test case that junior me did not. So as a vessel of “test instructions” they did not fulfill the needs.
Later in my career we had a nasty bug in production and testers were asked. Did you test this specific scenario? And looking at the reported test cases that was performed they did not contain enough details to be able to answer that question. So using them for test reporting was not enough. (Think login with a valid username and password what username and password did you actually use?)
And basically for most of the above mentioned things they have been failing at some point. Which then ties back to what others are saying. Your specific needs is what matters and for most specific needs there are better alternatives than test cases. But as a general tool serving all of them to some extent test cases is the only one that can do that.
Test Reporting - Screen captures, testing notes are better at capturing what you actually did.
Test Design - Checklists, Diagrams, Models, Story boards might serve you better.
Test Distribution - Testing Tours
Onboarding - Backpacking (you sit behind someone else that does it to learn instead of reading text)
For me it is important that you try to identify what purposes is important to you and then pick a tool that fulfills that best. If that is test cases go with test cases. If it is something else go with something else. To me it is unprofessional to say “we don’t use test cases” and then not explaining how you deal with those purposes. Either your alternative or a strategy that explains why they are unimportant. Commonly I’ve heard testers go “we do exploratory testing” so we do not design or report our testing. That is not “exploratory testing” that is unprofessional testing.