Timeline for How to write integration tests for a component oriented software platform
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 4, 2013 at 5:19 | vote | accept | twilker | ||
| Jun 3, 2013 at 14:45 | history | edited | Jan Hudec | CC BY-SA 3.0 |
added 109 characters in body
|
| Jun 3, 2013 at 14:40 | comment | added | Jan Hudec | @Yggdrasil: I'd start with the realistic configuration and progressively reduce the scope around the components that show problems. The realistic configuration is just one or few setups and it will show you which are the most problematic bits quickly. | |
| Jun 3, 2013 at 14:32 | comment | added | twilker | That was also our thought. But would you only setup the real dependencies and their dependencies and so on? Or would you test against a real life configuration - for example a configuration for a certain product? | |
| Jun 3, 2013 at 13:59 | history | answered | Jan Hudec | CC BY-SA 3.0 |