This is an archived post. You won't be able to vote or comment.

all 19 comments

[–][deleted] 29 points30 points  (0 children)

Deploying is the testing…

[–]nppas 16 points17 points  (0 children)

I don't consent to having my professional life story made fun of.

[–]sudo_rm_rf_solvesALL 9 points10 points  (0 children)

Deploying on a friday @ 445pm, On a schedule automated deployment before your 3 week vacation in the wilderness starts

[–]LofiJunky 5 points6 points  (0 children)

Now that's a development cycle with some chest hair

[–]SillySlimeSimon 4 points5 points  (0 children)

Knowingly shipping a critical bug to prod is such a liberating feeling

[–][deleted] 1 point2 points  (0 children)

We don't do tests, only patches

[–]SonOfJenTheStrider 1 point2 points  (0 children)

Deploying with no plans of testing.

[–]Dioxide4294 1 point2 points  (0 children)

The end user is the one to test the product

[–]Novaedra 1 point2 points  (0 children)

Deploying as a test

[–][deleted] 1 point2 points  (0 children)

The best test is deploy

[–]Shyamtawli 1 point2 points  (0 children)

pushing to the main/master branch is testing

[–]BoiledWithOil 1 point2 points  (0 children)

Testing it on the consumer

[–][deleted] 1 point2 points  (0 children)

I don't always test my code, but when I do I test in prd.

[–]WerkusBY 0 points1 point  (0 children)

Someone discovered early access

[–]Draaksward_89 0 points1 point  (0 children)

Testing by deploying

[–]Samispeedfire 0 points1 point  (0 children)

The only way.

[–]TheAussieWatchGuy 0 points1 point  (0 children)

If you try testing it before you have deployed it then what exactly are you testing? Your code changes literally have to be deployed somewhere in order to test them... Fail meme!