On 1/15/07, Ed Leafe <[EMAIL PROTECTED]> wrote: > On Jan 15, 2007, at 1:37 PM, sheila miguez wrote: > > >> If you change the code in the data tier, you must test > >> with every > >> backend and verify that every possible operation works correctly > >> before you even *think* about committing. This is not a trivial thing > >> to do. > > > > 1) Before committing to trunk, or before making a stable release? > > Before committing to the trunk. This is a vital area that affects > everyone.
Of course it is. I'm not denying that. I asked if you have different testing criteria before accepting changes because I'm doubting that you actually have 100% test case coverage of all possible combinations of a feature that you want to test. Not to mention that I doubt you have time to do 100% coverage of the test cases that you have come up with (scriptable or otherwise, unit or otherwise) before making a commit to the trunk. I'd expect that your coverage percentage is different based on what type of change you're committing, and I'd expect that you have different percentages for when you are preparing an official release. > > 2) Is doing regression testing against the test databases on your > > website the minimum, or do you test against something like Northwind > > too? > > I test such changes against the demo data on the site, as well as my > local stuff. I have VMs with each server type, so at a minimum I test > the demo data on each. People without access to your local data cannot run tests based on it. -- sheila _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
