＂Let me address the template question first.
In my opinion, templates sometimes cause more stumbling blocks than they they are worth. Every project is different, and not one will fit exactly into the template. I prefer to create a list of my own on what I plan to test. I'll read the requirements, and use a highlighter on the features so that when I create my test documents, I remember to test those features. Maybe a check list will help you.
Now the testing life cycle is actually very simply described. Remember when you were about 12 and were taught how to write a composition, that it contains 3 parts. Introduction, Body & Conclusion. That's the same with the testing life cycle.
- What you are planning to test (Test Plan)
- What you are testing (Test cases and steps)
- What you tested (Test Report)
Don't forget that you will be in continuous improvement afterwards, so you will be refining your tests for the next iteration of software.＂