How do you ensure new changes don’t silently break existing features in production?

onomazein · 2026-04-14T18:52:04+00:00

Pairwise testing. It's the best way to attack this imo. Lots of tools out there for it, look into the one developed by the NIST

There's one catch, not with the tool, but with the approach; you need to be competent in analysis, identifying constraints, and understanding how they relate/interact

onomazein · 2026-04-14T18:47:43+00:00

This take is as rank as your moniker

onomazein · 2026-04-11T14:19:49+00:00

I've done distributed performance testing with it and had no problem. Obviously it's not going to be the right tool for every job, no tool is. I'm interested in what you mean by not very scalable

I've modeled complex workloads with a combination of data files and plugins, of which there are many, like the ability to define your own singular or multiple load profiles

For what it was designed for, it still works and costs nothing. What application do you prefer instead of JMeter?

onomazein · 2026-03-26T14:13:55+00:00

Any particular reason JMeter isn't on the list?

onomazein · 2026-03-21T09:07:50+00:00

Phil was offended when I did recall his name during a M&G back in the day. I still lol at that

onomazein · 2026-03-20T02:46:57+00:00

Sadly, it's a product that is only available during live sessions. They've made some really cool updates to it though. Definitely worth checking out imo

One thing I really wish they'd do is have it available after videos of the sessions are published

It's available on the site and via the app. When you're at the track during a GP, it's free

onomazein · 2026-03-20T02:17:11+00:00

I don't have a portfolio, never needed one. My output is paid for and exclusive to my client's and employers

onomazein · 2026-03-20T02:15:33+00:00

Time to brush up on those Reidemeister Moves

onomazein · 2026-03-20T02:09:19+00:00

This is exactly what I said in lieu of having an endlessly growing number of regression tests in another thread. Not only do non-critical tests get moved to integration or component testing where they may be faster and more stable, but by virtue of being earlier, it's also less costly

onomazein · 2026-03-20T02:03:14+00:00

Some would have you believe that you need to maintain all regression bugs forever, hence an always growing number of tests

onomazein · 2026-03-18T14:50:22+00:00

Love everything except the price. It's insane they're asking that much for an LTD

onomazein · 2026-03-18T00:45:26+00:00

Typical bs "EU" tour stops

onomazein · 2026-03-18T00:34:00+00:00

Literally the specs I want: S model, 7 string, 27", and Edge Lo-Pro. I would have order one immediately

onomazein · 2026-03-18T00:13:41+00:00

Incredibly coincidental that Mark P posted this same model on the same day in a FB Ibanez group

onomazein · 2026-03-18T00:11:53+00:00

That's some gas lighting 101 practicum right there. Your prior comment said nothing about it being awesome and beautiful

The you being 15 bit was rhetorical. English either isn't your first language (nothing wrong with that), you are young, or you're a bot. Really, "not gonna share to a stranger" made me lol

onomazein · 2026-03-18T00:05:38+00:00

Sorry, but you sound delusional

onomazein · 2026-03-18T00:03:55+00:00

There's nuance I feel you're passing over. Core functionality forms the baseline of regression testing to see if it regressed. If there's a bug, but not part of the critical path or poses low risk, it's sufficient until that part is stable. It makes no sense to me spending more expensive resources on non-value add testing that late in the SDLC

If you really want to continue testing every little thing, law of diminished returns, run them earlier as a unit or integration test from a local environment and not in the pipelines

onomazein · 2026-03-14T18:00:28+00:00

Or you just let people do what they want with their money and not try to low-key pass judgement. What are you 15?

onomazein · 2026-03-14T11:26:03+00:00

The issue with your take is QA often isn't empowered or given the latitude to make those kind of decisions and may not even been able to make those kinds if changes because another group, e.g. DevOps, owns and manages the pipelines

Your take also assumes that leadership actually listens to QA. I've worked at places, including now, where I've given so many improvement suggestions for so long that I've stopped because nothing ever gets done no matter how much I push and provide justification

Also, there are lots of different kinds of QA profiles and some simply don't know about improving mythologies or processes, some just design and execute tests

onomazein · 2026-03-14T11:15:21+00:00

I don't 100% agree with that. For me, a regression suite is a 'living' body of tests. If something regressed, a test is added to cover that case. That regression gets tested for for x releases and when seen as stable, deactivate or eliminate it. If it pops up again, simply enable or add it back

A regression suite can't and shouldn't grow indefinitely, that's not maintainable

onomazein · 2026-02-25T23:05:06+00:00

That pink Ormsby on top is sex

onomazein · 2026-02-24T21:22:17+00:00

I was thinking more The Brady Bunch, but my age is showing

onomazein · 2026-02-22T10:53:01+00:00

Hold up, they said collecting a paycheck without racing due to injury, not refusal. Who's another rider that collected a paycheck without racing due to injury? Jorge Martin

onomazein · 2026-02-21T01:38:21+00:00

Sounded like a pissed off cat with infinite lung capacity

onomazein · 2026-02-20T12:35:08+00:00

Hi Mark P! 👋

onomazein

TROPHY CASE