Test plan help
Hi QA community,
I was hoping that someone can help me with something, I have been doing QA for about 8 months now, I had no prior QA experience only a keen eye for detail, patience and perseverance. The company I work for is a decent sized company with a small (but growing) digital department, there were no QA processes and procedures put in place before I started, I was the first QA person they ever had! They develop websites and games (HTML5, Flash and mobile games), I am responsible for doing all the QA across all projects. When I started, as I was very new, I didn't know about test plans and test cases, (although I had researched them, just never needed to put them together) I just procedurally worked through the projects and reported any bugs I had found onto our issue tracking software.
Now this is where I get to my question(s), our department is now being scaled up (which is really exciting!), but that means that I need to start putting together test plans (I was told to do this). I have done some research into test plans already and the documents are pretty intense and I'm having a hard job trying to make a generic one that I can change depending on the project. The thing is, I'm not sure if my boss wasn't sure what a test plan was and just wants me to put together a few test cases instead. In either case, I was hoping that someone can give me some help and advice, maybe suggest a test plan that I can use. I'll happy provide more information if needed.
Thanks in advance!
Originally Posted by pandafizz
I come from a similar situation except I'm more focused on project management and so gets involved with QA in that sense.
Let me tell you though that company size should not influence company structure. So I think it's important to understand first your company structure from a QA Manager/tester perspective.
For starters, can you share more about the ff:
1. What platform are you using to collaborate with other project team members? e.g. Podio, Trello, Office 365...etc.
2. What methodology/s does your team employ? e.g. SCRUM, waterfall, iterative, agile...etc.
I was surprised to find so many samples of test plans when I searched for them on Google. I would pick out topics that look useful from all of them and come up with your own recipe that matches your audience.
What I see currently the things are haphazard as there is no process and you test whatever comes in..
Testplan generally is a document where you put your approach, things that you require, conditions that you have to meet, in layman terms, you can say how you are testing the application you have to put in a documented form.
My suggestion here would be start with a basic test plan creation where first you think on how you want to carry out things, identify templates, testing types being used etc and then put in the test plan document.
I can send you a basic test plan document that you can start with and is easy to understand.. further you can enhance that. Let me know you email id.
Hope this helps.. Any queries let me know. Thanks.