Irene said: Without the solution details documented any where, as a BA/QA on this project, I am not clear how the testing should be performed
I think you have it backwards. What you want for effective test case generation IS solution independent requirements. What you don't want is implementation specific requirements.
And in order to create integrated solution independent requirements, a higher level approach is often needed - especially in Agile.
Thanks Tony!
I am trying to understand what "solution independent requirements" and "implementation specific requirements" are.
And also "in order to create integrated solution independent requirements, a higher level approach is often needed - especially in Agile." Could you help enlighten me as to the high level approach (meaning user stories only?) and the integrated solution independent requirements (ex. how is it different from user story or BRD)?
Thanks again in advance!
Although there are many ways to do testing right, most successful teams stick to these principles to avoid doing it wrong
Focus QA's efforts on understanding the intended functionality, the level of risk involved, and speccing out test cases to cover them that anyone can code to or execute.
Automate, automate, automate! Developers already have the skills to write test code, and nobody ever regretted training their QA team to do it, too.
Use code comments and renderers like javadoc or rdoc to represent test plans instead of spreadsheets. The code is the documentation.
Run automated tests against every build, and build several times throughout the day — a practice known as continuous integration — so you discover new defects when they're easiest to fix (which is now).
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: