|
I am currently working in a small agile team and I am trying to decide if a test plan is worth creating or if it is then what to include. Currently working on a story that I believe could do with some documentation to use as a guide and keep track of what is tested. I am unable to just create a script and follow that due to the nature of the story. |
||||
|
|
|
A test plan is worth creating if there is something that needs documented testing. It may be frustrating to see a test plan with only a few steps, but if you realize the purpose of the necessity of documentation, it doesn't matter how small the test plan is. You should include whatever it is that needs testing. Whether it's an anticipated UI response to interaction or a back-end component that gets updated, if it needs to be verified that an action occurred or did not occur, it should be included in the test plan. I work in an agile environment, and sometimes it requires test plans to be updated due to design changes. In an agile environment, that comes with the definition of the strategy. Just be sure to stay on top of changes that need to be made. |
|||
|
|
Welcome to SQA, Teague. Your test plan is part of a feedback loop. You convey something about the project to whoever is testing. They test the project, find some problems, and fail to find others. You incorporate what you observed into how you write your next test plan. It is all about paying attention and being open to changing what you do according to the circumstances. You probably have a hunch for the right depth for a test plan. Start there, then try what I just described. |
||||
|
|
