| || |
Testing Database-Drive Applications
Anyone out there with experience in creating testing models for database-driven applications? We are planning in 2004 to being to build database driven applications in which as set of business rules or workflows determine the functionality the end-user will see/use. The testing group is not at what i consider a high level of process maturity and we need to build a model that will test all of the functionality permutations driven out of the databases.
Re: Testing Database-Drive Applications
I don't see a need to depart from what is generally espoused here at this site or in related books about testing. The bottom line is that you need to define what it is you are going to test. Then you need to determine how you will test it in order to determine what resources you need in terms of people, environments, data, tools, etc.
If you have system specs, use-cases, requirements spec, functional specs - consider yourself to be fortunate. These documents in part or whole will be key to establishing what needs to be tested.
Speaking specifically to your comment about testing all functionality permutations...
Once you identify what you need to test, you can possibly calculate how many combinations and/or permutations you can actually test. The result of the calculation may surprise you. [img]images/icons/smile.gif[/img] That is where additional tools come into play to help you trim that number to something you can achieve before Sol turns into a red giant. [img]images/icons/smile.gif[/img]