Well, except the games that’ll only work on Switch and not Steam Deck.

There are more than few…

Yeah, I don’t get it. The only people looking at the results are devs, so we really don’t need the business requirement text.

I could maybe understand if product owners were creating the requirements in the feature files and devs were implementing them in the code, but that never happens. So the whole cucumber library thing we have going on just feels annoying.

It’s not the only thing we over-engineer. We have dependency injection when we only ever have one dependency (except in tests, in which case we could just use mocking). We take microservices to the extreme (we just broke out a couple hundred lines of code from a few thosand lines of code service). Our test code is unnecessarily reusable (test code is one place where DRY doesn’t really need to apply). And so on. This one in particular is especially annoying because it makes it harder to find the code without providing much benefit.

Our QAs seem to like it, so whatever. I’ll still complain though.

Nvidia is fine and has been for decades. I used Nvidia exclusively on Linux for ~10 years and it was fine. AMD is a better experience on rolling releases and for keeping up with Linux changes (e.g. Wayland), but Nvidia has always been fine, you just might be stuck on X or obeying something and miss out on some features like having two monitors with different refresh rates (IIRC that was only possible on Wayland).

Could it be correlated to Chinese New Year? I could see a ton of people in China suddenly playing and then not playing if most people get time off at the same time.

Does it happen every year around this time?

Alternative perspective, it could be related to the Great Firewall of a China, perhaps they made some rule adjustments and data came through that doesn’t normally come through.

Sure, and my issue isn’t that it’s capable of my requirements, but simple to use and meets those requirements. Simplicity is a quality all its own.

JUnit provides sufficient output to meet my requirements, so why overcomplicate it w/ Cucumber? AFAIK, cucumber tests in Java output JUinit as well (at least ours does), so what value exactly is Cucumber providing?

egress costs, which is their true and much sneakier vendor lock in trap.

Absolutely. That’s basically Oracle’a db strategy.

Things like this are why I’ll never use AWS, even if I get to a scale where it makes sense. I value the ability to switch to a different provider or self-host with my own hardware.

the only answer is government regulation

Ideally the market is competitive enough that regulation isn’t needed. But maybe that ship has sailed.

I agree with regulations like Net Neutrality, so I guess it would depend on how it’s worded. I’m just worried massive players like AWS would find ways to abuse any regulations we try to make to exclude others.

But yeah, I don’t pitch switching at work, because I’m not in charge of infra or really involved with it at all. I’m a SWE, not a devOPs or IT tech, so if I’m touching anything in Cloudwatch other than looking at logs, something has gone horribly wrong.

Oh sure, server grade stuff is cool, but rarely needed for a home lab.

These are for a mix of end to end and integration tests.

I mostly do unit tests as a dev, so our tests are simple enough that they don’t benefit from more structure than being grouped by suite. E.g.:

• AuthService
  • valid user creds can login
  • invalid user creds cannot login
  • non-existent user gets same error as wrong creds
• UserSettingsService
  • can change language
  • cannot set empty password

These don’t have long flows, so there’s no benefit to documenting steps (they usually have one step).

My complaint about cucumber/gherkin isn’t with documenting steps, it’s with managing them in separate files. We have a Service.feature file that documents the scenario and the ServiceTest.java that documents the steps. I don’t see the point in having those be separate files, especially since the only people defining inputs and scenarios are the devs (dedicated QA in our case). We occasionally have our BE devs help write a few tests, and every time it’s a struggle for them to figure out where everything is. It just feels over-engineered.

In unit tests, we parameterize our tests just like with cucumber, we just do so in the code. E.g. in Python:

@parameterized.expand([(1, 2), (2, 4)])
def test_duplicate(num, exp):
    res = dup(num)
    assert res == exp

I would much prefer something like that in our end to end and integration tests.

server grade budget.

And probably not server grade requirements.

Or maybe we just use it poorly. It doesn’t help that we use perhaps my least favorite language for testing: Java. I’ve written tons of integration tests, but we just used Python and unittest with some plugins to make output nicer, and it was pleasant enough.

Dating is all about going places you don’t like to meet people so also don’t want to be there, which makes literally any other option more appealing.

My SO and I met at a dance. I didn’t want to be there, and my SO thought it was tacky, so we had something immediately in common when I walked over to talk.

It’s a weird, unspoken cultural thing. If I go somewhere to have fun, I’m not interested in meeting new people, I’m interested in the activity.

I won’t tell you how to live your life.

Something is better than nothing, but keep looking.

I disagree. I’m a full-stack engineer, and every time I interact with our QA test suite in cucumber, I break out in hives. I hate keeping the gherkin feature file up to date with the test code, why so much complexity?

Demonstrate doing all three in the proper order. You get one cucumber.

Well yeah, cucumber is a Ruby/Java/etc testing framework and celery is a Python async task queue framework. Know what job you’re applying for, silly.

😁

Maybe that’s why I hate using it, or maybe I just hate testing frameworks that do more than run tests. Here’s what I want from a testing framework:

• run tests in classes or modules
• report output with some configurable name (javadoc comment, Python Docstring, etc)
• some way to parameterize tests with different inputs
• organized output that shows what failed
• if it’s an integration test, keep track of failures over time

Our QA uses cucumber and it works for them, so I only whine when I need to deal with it.

And lots of it.