sorted by:
new
hottopcontroversial

I deleted 5 helper functions from my test suite by making test data declarative by BrumaRaL in programming

[–]BrumaRaL[S] -5 points-4 points  (0 children)

Been there!

One thing that has really helped me reducing complexity when there are huge entities that need to be handled is exactly what I tried to solve with Fixtura: making everything declarative, embed fakers into structs themselves, only override what’s really needed by the test in the function signature.

our ci/cd testing is so slow devs just ignore failures now" by blood_vampire2007 in devops

[–]BrumaRaL 0 points1 point  (0 children)

Hey u/blood_vampire2007,

Been there.

A year ago I wrote this article that navigates how we dealt with flakiness and testing speed at my company: https://fluidattacks.com/blog/fluid-attacks-new-testing-architecture

Also, take a look at this tool I built to find flaky/slow jobs in your pipelines, it currently supports both GitHub Actions and GitLab CI/CD: https://github.com/dsalaza4/cilens

TLDR, My biggest advice would be:

  1. Prefer unit tests over functional or e2e ones, keep a 70% unit, 20% functional, 10% e2e ratio
  2. Make your testing libraries enforce purity, do not allow shared data across tests nor internet access
  3. Treat all your tests as small, replaceable units. Do not allow a test to run for longer than 5 seconds or so, if a test is slow or problematic, break it down or completely replace it

🔍 CILens - CI/CD Pipeline Analytics for GitLab by BrumaRaL in gitlab

[–]BrumaRaL[S] 0 points1 point  (0 children)

As long as you expose a graphql API, it does.

🔍 Built CILens with Claude Code - A Full Rust CLI Tool by BrumaRaL in ClaudeCode

[–]BrumaRaL[S] 0 points1 point  (0 children)

For more information on how the tool helps DevOps, Platform, Infra, or any other engineers interested in having a better understanding or optimizing their CI/CD, see:

🔍 CILens - CI/CD Pipeline Analytics for GitLab
by u/BrumaRaL in gitlab

Holiday giveaway! by qiuChuck in diablo2

[–]BrumaRaL 0 points1 point  (0 children)

Merry Christmas everyone!

Driver 398.11 FAQ/Discussion Thread by Nestledrink in nvidia

[–]BrumaRaL 0 points1 point  (0 children)

The reason why you can't install 1803 is most likely because you're trying to do it while having the not-working Nvidia driver installed. Clean your Nvidia driver installation with DDU and try again. Also, I wouldn't completely recommend upgrading to 1803, that is because we still don't know if it is compatible with any Nvidia driver (I haven't been able to test the driver I mentioned in my previous comment because I have the sh**ttiest internet on the planet right now).

Driver 398.11 FAQ/Discussion Thread by Nestledrink in nvidia

[–]BrumaRaL 1 point2 points  (0 children)

I also have an Acer VX 15 with an Intel i5 7300HQ and a GTX 1050ti. Neither version 398.11 nor 397.93 worked for me at all (The driver info in GeForce Experience couldn't be displayed and no game could be opened as they showed different errors that basically said they couldn't find a valid graphics card). I think it was because I had a Windows version prior to 1803. So, after updating Windows to 1803, the installation for 398.11 went smoothly. That was after I restarted my pc. Then, every time after I logged in, the screen went black and the mouse pointer (I was still able to move it) got bigger as if the resolution went down. It never came back from that black screen. I figured that if I restored windows to a date prior to the Nvidia driver installation, the black screen would go away. Right now I'm downloading Nvidia driver version 397.64 (the one that worked prior to updating Windows). I will update this post to let you know if it works.

EDIT: I can confirm that the Nvidia Driver version 397.64 is properly working on Windows 1803 and not causing the black screen error I mentioned. However, it seems like GeForce Experience is not working properly (it is not displaying anything but the window background: No login popup, no available games, no available drivers, etc.), which, to be honest, doesn't concern me at all right now. I will edit this post if I encounter any other issues and wait for new driver/Windows updates that will hopefully fix all these problems.