Testing Required

@testingrequired
123 Followers
69 Following
158 Posts
💻🔬 #developer && #tester 🛠️ Writer of test tools 🧠 ND 🎹🎛️ #synth manipulator 🎮 #gamedev | Changing hearts and minds about #testing and how it relates to #development
Rarely Updated Sitehttps://www.testingrequired.com
Githubhttps://testingrequired.github.io/
YouTubehttps://www.youtube.com/@testingrequired

#Programming is somewhere between #math and prose. Leans towards prescriptive. More rules and some guidelines.

#Testing is more like #music (music theory) and leans more descriptive. No rules because it's all guidelines.

Once again posting one of my favorite music/audio pieces. Gorgeous synth work. I love the progression of this track.

#synth #music #musicproduction #drone

"Alessandro Cortini - Trash Audio at the Apothecary 1-2" https://youtu.be/aZ155KLFoQM

Alessandro Cortini - Trash Audio at the Apothecary 1-2

YouTube

Well I'm casting about for my next role:

Want someone who can help set up teams for whole team quality, arm testers with knowledge, resources, and empowerment, set out quality visions, build internal communities, and has a focus on psychological safety? Hit me up!

I'd prefer a lead or principal level quality/coach role, but an interesting senior role could also be of interest.

MCR or remote pref, but occasional traveling is doable. Part time/4 days a week is also desired.

Boosts appreciated!

I was feeling like I was losing my mind when I saw missed or incorrect details on a ticket I created. I felt so bad until I saw it was a duplicate ticket of mine that someone else created. 💀

@kboyd @grmpyprogrammer yep.

1. write abstraction wrapper layer
2. write tests (of the consumers) with mocks for that layer
3. write integration tests for that layer that call the other API.

The tests in 2 run all the time as part of your automated tests of your consuming code, the tests in 3 run periodically, maybe not even automatically, and confirm that your integration with the 3rd party still works.

(and no, that's NOT how some of our tests work, but if I had a magic wand....)

"How do you test localisations", I asked. Received a test case. Mentioned I knew that, but I did not know why they go through the moves they do. Turns out neither did they.

Drilled down into risks:
- some (new) strings may not be localizable
- the original and the localised file may have differences in contents and a missing string may cause problems
- there may be missing translated texts
- the translated texts may be mistranslated
...

If you rely on "test case", document why not just how.

This is really cool and useful:

Using {Blocks} in Rust & Go for Fun & Profit
https://taylor.town/code-blocks

#code #coding #rust #programming #go #golang

Using {Blocks} in Rust & Go for Fun & Profit

The calm after a contentious on call rotation is like nothing. peace.