I moved into Excel, so that I can use VBA code to generate tests under program control. I actually automate the creation of manual scripts as well as compile versions of executable scripts for a range of test execution tools from the same basic input specifications. I also optimize (all-pairs like, but also triplets and quads) scripts and I apply translation tables, Governing Business Rule logic, and database profile references to make my scripts easy to maintain. This has saved me as much as 90% of the cost compared to projects that used conventional manual scripting approaches.
In different projects I've used
1. Self-developed DB in Lotus Notes (mostly)
2. Test Director (single customer used it)
3. Excel (once, when customer insisted on that)
There are certain benefits and drawback in each. Excel makes sense if only there is one tester. Specialized tools are matter of training and features used (different tools have different set of features).
?:the art of a constructive conflict perceived as a destructive diagnose.
Before I started as Tester in my company, they used Excel and Word.
There were also a few Test Cases in Test Director, but they have never been executed.
I write my Test Cases in Word and then import them in Test Director. Why Word, well it's much easier to check the spelling and for the creation I found it more clear. Because in Test Director you enter step by step. You only see the current step. I like an overview.