4 ms·
IME I've never needed one. You get a copy of prod and test against that. SPs are typically short, even when they're long their functionality tends to be well de
by throwaway_pdp09 6y ago
IME I've never needed one. You get a copy of prod and test against that. SPs are typically short, even when they're long their functionality tends to be well defined, it's never been a problem for me.
You certainly can and do add logging, this can be useful.
- mdoms 6y agoI don't know what industry you are in or what kind of data your users entrust in you, but "just get a copy of prod" is not an idea that would EVER fly in any organisation I have worked in. Developers do not get access to production customers' financial records, medical data or PII, ever.
- throwaway_pdp09 6y agoHands up, it's a fair point. I've worked with data sets that are mainly large aggregates of public data so security isn't an issue. It's the code that's carefully protected. One exception is having access to that data because I was working ON the prod server. Read that again. It was deeply uncomfortable to work like this. Very worrying every day.
- throwaway201103 6y agoIn those cases you have a set of test data that you use for development and testing. It's not like you can attach a Visual Studio debugger to production either.