Timeline for Databases and Unit/Integration Testing
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 15, 2011 at 21:44 | comment | added | Jalayn | The big setup phase that inserts data useful to different test cases may only be useful for integration tests where you need to check different parts of the application working together. It may be worth having this big common set of "inserts" because you will most likely need some of them for other integration tests. Otherwise, if we're talking only pure unit testing, I'm absolutely for having one set of data to insert for each test case. | |
| Aug 15, 2011 at 21:13 | comment | added | ryanzec | Wouldn't I rather be creating the the parts of the database needed each for for the test than have someone accidentally modify the data in a way that causes a failure? Having to make sure the data is correct when a test fails seems like something that can be prevented. | |
| Aug 15, 2011 at 19:46 | history | answered | Jalayn | CC BY-SA 3.0 |