Welcome to Stephen. Sure, I mean I’m not on the pro circuit here myself, just been doing this a long time. but the reason you might write down your test plan is to help the next person, as well as yourself. A test report is often not a thing anyone will look at unless you are in a regulated industry. But I find it helps me track my progress longer term, while the test plan helps me track my goals day to day.
I’m a big fan of automated testing, probably because my previous career was in C/C++, so I like to have a excel sheet of all the manual tests and rank ones that I think can be automated with some benefit/value and confidence. That same sheet doubles as my test report for manual testing. So generally my plan is to automate as many as possible over time so that I don’t have to execute those manually. Trouble is, that sheet will grow and grow. The big part of my plan is however making sure I have a realistic idea of how the release works, who will be deciding on hitting the big red button, what we can do to help if we have to roll back/forward.
A podcasting app sounds way interesting, and will have so many aspects to cover because it involves so many components, and so many use cases. I assume you are talking Production here, not consumption. All kinds of things like RSS feed formats and the continuous updates and things like download stats now being shared as well as review support makes this a beast that wants some amount of focus to stop getting lost in. You are welcome to PM me, I normally only log in the mornings, and the rest of the time you stand a chance of catching one of the regulars when we drop into the google hangout www.bit.ly/testerhangout (google account required)