Attention is currently required from: neels, pespin, fixeria.
1 comment:
Patchset:
I personally see no reason for using the mockup stuff in the ttcn3 tests, and hence no reason for th […]
I tend to agree with pespin's assessment. We shouldn't have development/debug only features [enabled] in normal production builds. Particularlly not if they make it look like some objects existed, while in reality they don't. Looks like a huge source of potential user confusion.
Also, for the TTCN-3 tests, I think in general the goal should be to run the unmodified program just like in production, with all of its interfaces etc.
If for some reason we cannot do that in our existing normal jenkins slaves or docker containers, we can always use some kind of special slaves (we already do for example for testing the E1 / frame relay bits.
So I think if some testing/mocking is happening, it should happen on the tester (application, OS, VM, ...) side, and not inside the implementation-under-test.
VTY tests is a different special case, and we're not arguing about that here.
To view, visit change 28986. To unsubscribe, or for help writing mail filters, visit settings.