Testers

[vetran]

Cannot put live data in test environment
don't get me wrong we are not talking lots of bugs and the dev team get judged on that but the initial requester has to test and sign off prior to deployment to prod environments

Also erm.... Agile kinda relies on dev.test.rework

the data supplied in Dev is sanitised or made up but representative of data needed for calculations .

You may be able to put Real data in it will probably not be live unless you can get permission, i.e. it can be earlier years or sanitised replace names / identifying characteristics with other values.

Testers and customers should have checked with real data.

I have done the data security courses and we have very active works councils. Surprised they managed it with all the doughnuts.

[tomtomagain]

We're right at the top, get used to it

Anyone doing the work is at the bottom.

Anyone with "Architecture" or "Strategy" in the role title is a spectator on the sidelines.

Anyone with "Project", "Programme", "Test" or "Delivery" followed by "Manager" in the role title is taking the stress AND the blame.

[d000hg]

Anyone doing the work is at the bottom.

Anyone with "Architecture" or "Strategy" in the role title is a spectator on the sidelines.

Anyone with "Project", "Programme", "Test" or "Delivery" followed by "Manager" in the role title is taking the stress AND the blame.

This kind of thinking is why the technical folk remain at the bottom, they are incapable of recognising the worth of anything else other than the technical side.

[TestMangler]

the data supplied in Dev is sanitised or made up but representative of data needed for calculations .

You may be able to put Real data in it will probably not be live unless you can get permission, i.e. it can be earlier years or sanitised replace names / identifying characteristics with other values.



I have done the data security courses and we have very active works councils. Surprised they managed it with all the doughnuts.

I've worked for all the major retail banks pretty much, in a test management capacity and I don't think I've been in one who actually sanitises their data when loading prod cuts into test and dev environments, unless you count the setting of passwords as 'sanitising'.

[tomtomagain]

This kind of thinking is why the technical folk remain at the bottom, they are incapable of recognising the worth of anything else other than the technical side.

Show me the org chart of any large corporation and you'll find that the "do-ers" are actually at the bottom.

Some people like doing the work and focus on that. Others focus purely on how they'll get their next role.

[vetran]

I've worked for all the major retail banks pretty much, in a test management capacity and I don't think I've been in one who actually sanitises their data when loading prod cuts into test and dev environments, unless you count the setting of passwords as 'sanitising'.

There is frequently a difference between best practice & reality.

http://www.oracle.com/us/products/da...ces-161213.pdf

Data Obfuscation - managing data privacy in development and test environments

we know what should be done getting the bill payer to do it is a completely different matter.

[CheeseSlice]

Where exactly do they fit in the pecking order?

Got one here and she's a right little bossy boots. Always referring to us as "my developers".

Gets right on my tits.

The way I see it is that it is us developers that do the jokes....

(..mind you, some of the places I've worked, that statement could be taken literally)

I've got a lot of respect for testers compared with developers.

Too many times have I seen a developer sit back in their chair slowly sipping a cappuccino trying to explain to a tester that some blatantly tulipy code with no error handling is just working 'by design' or 'as per the spec'.

"Yes it crashes and beeps when you do that, but that's because you put the wrong values in. Bug closed as 'Wont Fix'. Reason 'Working by design' "

[TestMangler]

There is frequently a difference between best practice & reality.

http://www.oracle.com/us/products/da...ces-161213.pdf

Data Obfuscation - managing data privacy in development and test environments

we know what should be done getting the bill payer to do it is a completely different matter.

I'm aware of that

You were the one that said data was sanitised, when generally, it isn't.

[d000hg]

Show me the org chart of any large corporation and you'll find that the "do-ers" are actually at the bottom.

Some people like doing the work and focus on that. Others focus purely on how they'll get their next role.

Again - the techy folk are SO anxious to tell everyone why they're better. Get over yourself. Managing IS doing. Selling IS doing. Designing the whole darn thing on paper IS doing. Just because you don't enjoy those parts doesn't stop them being valuable, the inability to see that marks you out as just another nerd who cannot understand the world outside their computer

[vetran]

I'm aware of that

You were the one that said data was sanitised, when generally, it isn't.

[QUOTE]should have supplied data for them to test in Dev[/QUOTE]

as I say best practices are not always reality. I like to start with BP and get used to being negotiated down, my email says sanitised, theirs says lets copy from production = my large hairy butt is covered.