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.
> 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.
> 3) Do you also test every platform? (You have a macbook right? so you
> can do that. which is neat). If a developer doesn't have access to a
> platform or test server, what should the practice be? Create a branch
> with the fixes and ask for help testing it before merge?
OS platform is irrelevant for data tier testing. When I make UI
changes, then yes, I test with Mac, Windows and Linux. Frequently I
will commit after doing full testing on Mac, so that I can grab the
updates and test them on Windows and Linux. I don't commit them until
I'm ready to run those tests, though, so that I can either confirm
the change or roll it back if those tests don't work out.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
