Users will test, don’t waste your energy.

Wow, that’s big. Thank you for the clarification.

I’m not familiar with the service, can someone explain? Like, are all pipelines on Azure affected? Or is it some internal stuff where a company relying on paid tech forgot to pay for it?

0% of Rust smh

Maybe you’re just intolerable.

I’m glad we aren’t friends.

Bro is trying to cope with the fact that he bought same house twice 💀

How’s this programmer humor?

Alright, this is my first contribution to an open-source project, albeit indirect. I’ll drink to that!

Somebody should tell Albert and the others, they can let this method go.

“p” should be lowercase, the metalbags aren’t that good yet.

You’re more cautious with a meme than that lady with a grenade.

Since I’m already using Bitwarden, generating and storing passwords is easy. I use my name as the username, though that user doesn’t have admin privileges.

Also awful people tend to use same awful instances, so you can block a lot of awful people in just a couple of clicks!

It’s the same format with the same people. The only difference is that Lemmy is decentralized. Besides, it isn’t monetized at the moment, so there are no ads or other nuisances.

That sounds strange. I cannot comment on your particular case without seeing the test artifacts.

Generally speaking, there is nothing wrong with tests that ensure bad input doesn’t break the system, as this can easily lead to incorrect system states, damage to the environment, loss of data, money, reputation, and even lives - although most systems are not critical enough to threaten lives.

You wouldn’t need QAs if you only needed to validate that the product meets the requirements. In a typical company, many people are involved in that process. This includes the developer who wrote the code, the developer who reviewed it, and the people who conduct acceptance testing, among others. If your developers produce code that doesn’t meet the requirements, you’re in trouble.

I’m not saying that QA shouldn’t validate whether the system meets the requirements, but you don’t want them to do just that.

A QA engineer walks into a bar and asks where the bathroom is. The bar bursts into flames. The product owner says that the bar can be shipped anyway.

Great, it’s reliable and enforces design patterns!

I’m not surprised. A cube can’t be round. That’s an obvious design flaw.

I still don’t understand. I assume there is a plugin that enables github annotations in the code. But why would anyone need that?