STOP. TESTING. IN. PRODUCTION.
STOP. TESTING. IN. PRODUCTION.
STOP. TESTING. IN. PRODUCTION.
STOP. TESTING. IN. PRODUCTION.

@rutee07 How much?

@Jilano No, but Semenology

Who says it's testing? It's exploring.
*Do-do-do-do-dora*

Best testing is production testing.

Probably not the best idea... but without a doubt the most reliable way to find out how it will work in production is... in production.

There's no testing in production if you just never test your code

It's called "shift right," friend.

When this 3rd party has a not so prod env, then sure... I'll stop testing in prod.

The world will end if I dont

@C0D4 Yeah in that case that makes total sense.

But what I saw was a web application that has dev, staging, pre production , and production environments. The three other environments work perfectly fine and are best as test candidates.

Yet, a moron decides to pollute the production data with his dumb tests! He still does that after being advised against it!!!

The fact that I have to read pages of test data just to get to my target and filter those out if I want to make a useful chart is just absurd in this scenario. Hence the rant.

@aj7397 Purgatory.

Revoke of database access.

Done.

@aj7397 see... that I can't justify.

I at least mock the 3rd party in UAT so that it's expected behaviour can be confirmed to be working for my end.
But there are times actually testing E2E has to be done in prod.

But outside that kind of problem, no, especially if you have staging / dev environements to test with.

I agree fully! That's why we run production on testing!

test message 123

Who? Me?

Na

in freelancing, many of the clients( that I've encountered) don't give a shit about different staging environments like Dev qa prod etc.. they just wanna have end product that's it

Ultimately, I’d argue there is no test EXCEPT production.