Got a source for the majority claim?

Now install tools that are only available as github released binaries. And ensure that hashes match for that. Maybe install a tool that needs to be compiled.

What if, get this, we put the bash scripts in yaml. And then put it in kubernetes.

And what is the token in the link?

End-to-end tests are basically non-deterministic state machines. Flakiness can come from any point in the test: bad tests, bad state management, conflicting tests, network hiccups, etc.

Your goal is to reduce every single point of that flakiness. Just make sure you keep track of it. Sometimes flakiness in tests is really pointing at flakiness in the product itself.

Some things that can help reduce that flakiness:

• Dedicated network
• No external dependencies
• Polling instead of static waits/sleeps

Consider that a ‘username+password’ is much harder to ‘revoke’ individually. As in, you can have 3-4 API keys in use, and can revoke any one of them without having to change a password.

You can also change password independently of the keys, or have it linked so keys are revoked on a password change. It also allows traceability as to where accesses are coming from (auditability). If everything is using the same client-id+secret (or usn/pwd), you don’t know which ‘client’ is doing what.

It’s the sort of thing that makes me really, really sad for the people working there. That crazy breakneck pace cannot be good for mental health.

I think too many people forgot the satire in the original name.