Slashdot Mirror
Strategies for Test Databases?
youngcfan asks: "I've been tasked with finding strategies for a test database that can be used effectively by both software developers and the QA team. We're a J2EE shop with most of the interesting pieces of the application interacting heavily with the database -- so we need to test it. We're ramping up on JUnit, but are looking for ways to test the database-driven pieces of code. Since QA needs the same database for functional testing separate from developers' unit tests, DBUnit doesn't seem to suffice. We also have the challenge of working on multiple releases at the same time, which only complicates how and when to add new data to the test database in a way that's useful and valid for everyone. We're looking for strategies for using a test database in a way that meets both the QA's and the developers' needs, works for multiple releases, and isn't a heavy burden to maintain given that the schema and code can change anytime before any of the multiple upcoming releases. Any suggestions?"
Hey you ! out there in the cold
Getting lonely, getting old, can you feel me
Hey you ! Standing in the aisles
With itchy feet and fading smiles, can you feel me
Hey you ! don't help them to bury the light
Don't give in without a fight.
Hey you ! out there on your own
sitting naked by the phone would you touch me
Hey you ! with your ear against the wall
Waiting for someone to call out would you touch me
Hey you ! would you help me to carry the stone
Open your heart, I'm coming home
But it was only a fantasy
The wall was too high as you can see
No matter how he tried he could not break free
And the worms ate into his brain.
Hey you ! out there on the road
Doing what you're told, can you help me
Hey you ! out there beyond the wall
Breaking bottles in the hall, can you help me
Hey you ! don't tell me there's no hope at all
Together we stand, divided we fall.
The ascii goatse has really been ruined by the Slashdot redesign. You can barely even see it anymore.