in reply to Re^2: "deep" unit testing
in thread "deep" unit testing
Can you elaborate a bit on what we're talking about in regards to timing? 5ms, 100ms etc?
Can you also explain in a bit more detail the nature of what is being tested? No need to go to extremes here, just enough so we have a better idea of the why regarding such time-sensitive (and non-additive-to-codebase) testing.
Is mocking out pieces of specific tests an option? Do you store data externally so that you can test against it so timing isn't so critical?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: "deep" unit testing
by LanX (Saint) on Mar 27, 2019 at 20:58 UTC | |
by stevieb (Canon) on Mar 28, 2019 at 02:21 UTC | |
by Your Mother (Archbishop) on Mar 28, 2019 at 02:36 UTC |