Maaret Pyhäjärvi
@maaretp.bsky.social
150 followers 210 following 110 posts
🇫🇮Tester of products and organizations. Regretful Manager. Exploratory tester, (Polyglot) Programmer, Speaker, Author, Conference Designer. She/Her. [email protected]
Posts Media Videos Starter Packs
maaretp.bsky.social
Fake screenshot alert! The message, my opinion, is very real though. All software consultants (with Finnish rate card) should invoice at least 100 euros.
Newer needs support and training, on their employees dime.
When customers switch contractors, consultants need time to find the next gig.
Reposted by Maaret Pyhäjärvi
charity.wtf
Any asshole can build an org where the smartest, most experienced engineers in the world can get shit done.

A truly great engineering org is one where normal, workaday software engineers, with decent skills and ordinary experience, can move fast, ship code, and move the business forward day by day.
maaretp.bsky.social
To run a demo with an open source test tool today, I needed to start my day with getting the tool fixed with a new release. Who tests the tests rings true.
maaretp.bsky.social
It's coming up, and I can't wait: #FroGSConf. A week from now, Saturday. I have a hands-on session in mind I want to run on #testing, but I also would like to do one on #QualityEngineering and the practical change to allow quality to be everyone's business. frogsconf.nl - it's free.
maaretp.bsky.social
There's appearance of success (local stories of success), without sustainable success over time in #TestAutomation. So I gave them labels and one-liners because this style of thinking helps me structure my ideas.
Screenshot with mostly text. 
Test Automation. Successful yet not sustainable. 
1. Gym Membership. Tools meed people operating them. 
2. Island of One. No success without succession. 
3. Not Invented Here. Reinventing frameworks is fun.
maaretp.bsky.social
Comparing the feedback ChatGPT gives based on a screenshot to what a human (other than me) does in an hour. Wake up, one-up time. Tools like this are an external imagination. Use them, but don't rely on them alone.
maaretp.bsky.social
Don't we all test demo versions of to do app for fun and write about it? visible-quality.blogspot.com/2025/02/that...

Turns out we don't need to seed bugs to find bugs. But we need better skills in analyzing functionality.
That Pesky ToDo app
Ideas and experiences on software testing, software development, conference speaking and organizing.
visible-quality.blogspot.com
maaretp.bsky.social
#Saavutettavuus #Suomi. Käynnissä kaksi merkittävää laajennosta: uusi direktiivi ja uusi tulkinta. Toimenpiteet tiivistettynä: saavutettavuus kuntoon, saavutettavuusseloste kuntoon, ja aktiivinen raportointi puutteista.
Kuva jossa enimmäkseen tekstiä. 
Saavutettavuus (Suomi)
Laajenemassa: EU-lainsäädäntö siirtymäajan loppusuoralla
Täsmentynyt tulkinta soveltamislaajuudesta julkishallinnolle 

Mitä tehdä 1-2-3
1 Saavutettavuus kuntoon
2 Saavutettavuusseloste ja uusi valvova viranomainen
3 Ilmoitusvelvollisuus puutteista
maaretp.bsky.social
On ideas that drive testing, shapes of context is quite a powerful one. This weeks shapes for me are:
1. Remote testing, local ownership.
2. Platform testing. Testing pyramid would be irrelevant.
3. Build and document with automation. Close collaboration in teams owning quality.
maaretp.bsky.social
Listening to @annemariecharrett.com make the point that "quality engineering is not a testing model but an engineering model". It's a model that integrates quality practices, in a variety people don't always recognize as testing, into engineering.
maaretp.bsky.social
Another idea that drives how I now frame testing is scaling. It came along with being able to run thousands of tests a day, sourced from tens of teams in internal open source style. People can't hold the knowledge. People can complete circles but holding it, we need a system to do that for us.
maaretp.bsky.social
Earlier this week, I was reminded of thinking of test strategy 10 years ago, with an experience report at a peer conference. Then I coined four ideas:
Knowing product. Delivering professionally. Actionable information first. Releasing in production when done.
The last included building capability.
Sketchnote of 'Where is the strategy with an agile team' by Zeger Van Hese (testsidestory) 10 years ago as he sketched a peer workshop session on my experience report.
maaretp.bsky.social
While I would frame the ideas driving test automation with capturing things into pipelines, I also would frame it with the idea that *anything else in testing could happen while working towards automation*.
maaretp.bsky.social
Ideas of new capabilities are driven by changes in the world. Accessibility this year, driven by the changes in EU legislation, as well as Finnish interpretations of already existing legislation. AI and the need to intertwine it. OSS composition analysis and risks in ownership.
maaretp.bsky.social
Another idea that drives testing is that *professional testers as proxy for real users are poor substitute*. This increases the aspects of "social" in testing. You must meet real users. You must facilitate conversations for whole teams for real users. And you must go to logs with data of real users.
maaretp.bsky.social
Essentially, with the parts that focus on testing of applications, our ideas that drive testing are founded on the idea that work needs to continue when we are no longer around. Organizational resiliency requires all of us to care to leave things behind. This is why we *capture things in pipelines.*
maaretp.bsky.social
We may say "shift left" and "shift right", but in fact we are in the process of completing a circle, but with a social transformation: *testing is too important to be left just for testers, but also too important to be left without testers*.
maaretp.bsky.social
The first idea that drives testing is *testing is bigger than testing of apps*. You know, the fact that I am a tester yet I test ideas, organizations and sometimes people's patience. A common way of describing this is to point at every stage of DevOps cycle and say "you test here".
maaretp.bsky.social
In preparation for 'Testing strategies for business resilience 2025' today (info.saucelabs.com/business-res...), I am revisiting ideas that drive testing = strategy.

I have been collecting and structuring ideas that drive change, in mostly four categories.
Slide of "Future is already here, it's just not evenly divided" with four main areas in which change is ongoing: 1) automation, 2) opportunity cost, 3) Social and 4) next generation artifacts (AI).
maaretp.bsky.social
I have not managed to make sense of what to write here, what on LinkedIn and what on Mastodon. I am still mostly elsewhere even if I appreciate that here algorithm makes me happy by showing me the tech bubble I belong with.
Reposted by Maaret Pyhäjärvi
auschwitzmemorial.bsky.social
Auschwitz was at the end of a long process. It did not start from gas chambers.

This hatred was gradually developed by humans. From ideas, words, stereotypes & prejudice through legal exclusion, dehumanization & escalating violence... to systematic and industrial murder.

Auschwitz took time.
A bird's-eye view of a former Auschwitz II-Birkenau camp showing a wide dirt pathway flanked by parallel rows of barbed-wire fences. Groups of visitors walk along the path, surrounded by the remnants of brick structures and barracks, now reduced to foundations. Green grass contrasts with the somber history of the site, as the path leads toward a guard tower in the distance.
maaretp.bsky.social
12th time is not the charm but I represent, again, for the 12th time on Finnish Tester of the Year award. There were a few years in between when I refused them adding me as nominee, because it is silly how there are no other women (when there are LOTS). www.tieturi.fi/aanesta-vuod...
Äänestä Vuoden testaajaa 2024 - Tieturi
Kuka on Vuoden testaaja 2024? Vuoden testaaja on Tieturin ja TestausOSYn vuosittain jakama testauksen tunnustuspalkinto, joka nostaa esiin testauksen merkityksen ja sen huippuosaajat. Vuoden testaaja ...
www.tieturi.fi