Canenald

Literally the worst pilot in TEST

[Canenald @Canenald]

@tottinge I would add continuous delivery and culture of learning, and name it after me 😎

[Canenald @Canenald]

@tottinge It looks like the same person was generating a similar bullshit document on agility vs something else and pasted agility into the wrong document by mistake.

[Canenald @Canenald]

@matteocollina I prefer environment variables to have higher precedence because it's easier to have the defaults in the .env file and do one-time overrides through cli.

[Canenald @Canenald]

@allenholub If you are really troubled by multiple assertions, most runners allow you to write custom assertions and then you can have the illusion of checking only one thing 😉

[Canenald @Canenald]

@allenholub I'd say a single setup and action part per test case is ideal. Having multiple assertions is fine. You bring the thing under test to the desired state and then assert on it. Doesn't matter whether you need one or more of the low level assertions your test runner offers.

[Canenald @Canenald]

@alexbunardzic @yarlson It collapses to a single local stage which is either deterministic or non-deterministic, but it's not real because it can't be both local and real at the same time. Or something like that.

[Canenald @Canenald]

@allenholub @ThadOfSphere Imagine being hired as Ineffective Software Engineer.

[Canenald @Canenald]

@davefarley77 risk

[Canenald @Canenald]

@NotMyAgile Nah, I tried but they wouldn't have me. I suggested not working on everything at once.

[Canenald @Canenald]

@JLarky @DorShinar @jarredsumner That's not how it works.

[Canenald @Canenald]

@acemarke @wesbos At this point, you decide your changes are ok and you stage and commit only some of the lines, leaving others unstaged.

Doesn't that basically mean what is commited is not what you tested?

[Canenald @Canenald]

@acemarke @wesbos I guess I don't understand the value of this so please help.

You have some changes in your code. You are testing them somehow, either manually and using tests, or a mix of the two, and at some point you are confident your changes are ok.

[Canenald @Canenald]

@alexbunardzic cuz I'm scrolling the Internets half the time

[Canenald @Canenald]

@alexbunardzic idk, you brought it up. I'm saying with ci/cd you can still take something you think you might need through the pipeline

[Canenald @Canenald]

@adymitruk @vandot @d_stepanovic Yes, let's make another branch to check if everything is working with a version of the code that is highly unlikely to ever end up in production 🤡

[Canenald @Canenald]

@vandot @allenholub @d_stepanovic TBD and CD are strongly dependent on teamwork. Devs used to working in isolation with no responsibility except for their own code find them difficult to comprehend.

[Canenald @Canenald]

@vandot @allenholub @d_stepanovic Test locally yes. Also run commit stage tests in CI. If those pass, deploy and run more tests in testing env. If anything fails, the whole team stops until the pipeline is green again.

[Canenald @Canenald]

@alexbunardzic I'd be honored, but idk, I like React 😂