Reminders for 2024 (but it is applicable all the time) for testers!
https://www.linkedin.com/pulse/3-reminders-testers-2024-ivan-karaman-uri5e
https://www.linkedin.com/pulse/3-reminders-testers-2024-ivan-karaman-uri5e
Linkedin
3 reminders for testers in 2024
1 - Embrace working with developers And I’m not talking about “having an occasional conversation with them” 🤣 Actually work closely with your software engineers. Brainstorm, pair test, pair program.
Simple example on how to automate 2FA code generation!
https://www.linkedin.com/pulse/automating-2fa-hard-impossible-ivan-karaman-esgfc
https://www.linkedin.com/pulse/automating-2fa-hard-impossible-ivan-karaman-esgfc
Linkedin
Automating 2FA is hard? Impossible? Or…
It is not hard! In fact, it's quite easy..
I think a lot of people use wrong words when they talk about testing...
Imagine a phrase: "I do a positive exploratory black box ui system acceptance test"
...and this is not a gibberish, it makes some sense! All these words describe "different kinds" of testing, so using them in one sentence is ok (at least grammatically 😁).
https://www.linkedin.com/pulse/software-testing-categories-ivan-karaman-wrr2c
Imagine a phrase: "I do a positive exploratory black box ui system acceptance test"
...and this is not a gibberish, it makes some sense! All these words describe "different kinds" of testing, so using them in one sentence is ok (at least grammatically 😁).
https://www.linkedin.com/pulse/software-testing-categories-ivan-karaman-wrr2c
Linkedin
Software testing categories visualised
I have a problem with software testing. It has way too many different types, names, and dimensions! Meaning talking about it is HARD! One can say: I do a positive exploratory black box ui system acceptance test .
Pesticide paradox is one of the things every tester encounters quite early in their career. But are you using an original definition, or a distorted ISTQB one? 😜
https://www.linkedin.com/pulse/paradox-pesticide-ivan-karaman-8nayc/
https://www.linkedin.com/pulse/paradox-pesticide-ivan-karaman-8nayc/
Linkedin
Paradox of the Pesticide Paradox
We need to talk! Talk about the “pesticide paradox”! Testers seem to use this term without digging into “Where did it come from?” and “What is the original quote?”. And I am also guilty of this… I am one of those people! 😅 I knew this term for years, but…
What is a "test automation framework"?
Good question!
https://www.linkedin.com/pulse/mythical-beast-called-test-automation-framework-ivan-karaman-teq4c
Good question!
https://www.linkedin.com/pulse/mythical-beast-called-test-automation-framework-ivan-karaman-teq4c
Linkedin
Mythical beast called "Test automation framework"
Beginner test automation engineers struggle with many things. One of them is the confusion around this: “What is the test automation framework?” This phrase is even harder for people with English as a second language! Framework?? 😕 The goal of this article…
What if I tell you that "testing in production" happens no matter if you do it or not? Customers do it for you, haha! 😂
Is it a good idea for you to do it or do you need to rely more on observability (spoiler: the latter!)?
https://www.linkedin.com/pulse/testing-production-yes-observability-ivan-karaman-plfbc/
Is it a good idea for you to do it or do you need to rely more on observability (spoiler: the latter!)?
https://www.linkedin.com/pulse/testing-production-yes-observability-ivan-karaman-plfbc/
Linkedin
“No” to Testing in Production!?… “Yes” to Observability?👀
🕵️A few days ago I was lurking on the real estate website and found a very curious listing… it was a TEST LISTING! On the customer-facing website! Of course, I looked around for more! And, of course, I found more… 😃 From this article, you will learn: is testing…
Practical guide on naming things while coding.
Use this pattern:
Horrible → acceptable → good → perfect
https://www.linkedin.com/pulse/how-name-things-while-writing-code-ivan-karaman-0w6fc
Use this pattern:
Horrible → acceptable → good → perfect
https://www.linkedin.com/pulse/how-name-things-while-writing-code-ivan-karaman-0w6fc
Linkedin
How to name things while writing code
Naming is hard! Did you ever struggle with naming a variable? A method? A file? 🤕 I am sure you have seen code examples like these: This naming style is common for less experienced test automation engineers (and, who are we kidding, developers) meaning it…
❤2
Doing first steps as a "test automation engineer"?
This article is for you! ❤️
https://www.linkedin.com/pulse/first-most-important-step-road-test-engineer-ivan-karaman-ekqlc
This article is for you! ❤️
https://www.linkedin.com/pulse/first-most-important-step-road-test-engineer-ivan-karaman-ekqlc
Linkedin
The first (and most important) step on the road to a “Test Engineer”
In my "Ask me anything" meetings I often speak to testers/QAs at the beginning of their “test automation” journey. Some of them ask: How do I become a “Test Automation Engineer”? This article will help you to understand the “first steps” of this “Test Engineer”…
👍2
Dive into the analysis that proves that paying for "test automation" education is worth the money you invest into it!
https://www.linkedin.com/pulse/calculate-paying-test-automation-lessons-any-other-worth-ivan-karaman-td2yc/
https://www.linkedin.com/pulse/calculate-paying-test-automation-lessons-any-other-worth-ivan-karaman-td2yc/
Linkedin
Calculate if paying for “test automation lessons” (or any other education) is worth it!
Do you ever want to buy something but think “Nah, too expensive, I’m not going to…”.🤔 I do! A lot! Every time one faces a yes/no choice they have to answer the question: Is it worth it? This article will analyze the visible and invisible components of the…
❤2👍2👏1
This is why I love Twitter!
Sometimes you can get SO MUCH wisdom from a random post by reading replies...
Take this one from DHH:
| "HEY today has some 300-odd system tests. We're going to cut that number way down. The sunk cost fallacy has kept us running this brittle, cumbersome suite for too long. Time to cut our losses, reduce system tests to a much smaller part of the equation."
https://x.com/dhh/status/1791552150038024424
🤔What can we extract from the buzz in replies and quotes around it?
(...some screenshots and more links in comments...)
Sometimes you can get SO MUCH wisdom from a random post by reading replies...
Take this one from DHH:
| "HEY today has some 300-odd system tests. We're going to cut that number way down. The sunk cost fallacy has kept us running this brittle, cumbersome suite for too long. Time to cut our losses, reduce system tests to a much smaller part of the equation."
https://x.com/dhh/status/1791552150038024424
🤔What can we extract from the buzz in replies and quotes around it?
(...some screenshots and more links in comments...)
X (formerly Twitter)
DHH (@dhh) on X
HEY today has some 300-odd system tests. We're going to cut that number way down. The sunk cost fallacy has kept us running this brittle, cumbersome suite for too long. Time to cut our losses, reduce system tests to a much smaller part of the equation." …
🤓4
Would any of you like to have an "early access" to the articles that I create? 🤔
Benefit for me is the feedback (highlighting the blindspots), benefit for you is, well, early access and a chance to work with me! 🤣
Benefit for me is the feedback (highlighting the blindspots), benefit for you is, well, early access and a chance to work with me! 🤣
Anonymous Poll
100%
Hell yes!
0%
No, thanks...
Friday afternoons are for the good reads!
I want to share with you one of my "all time favourite" articles ❤️
It is about "lemons"! 🤣
It explains a SURPRISING DYNAMICS of the hiring market! If you are looking for a job, or looking to hire somebody, reading this might be useful!
http://danluu.com/hiring-lemons/
I want to share with you one of my "all time favourite" articles ❤️
It is about "lemons"! 🤣
It explains a SURPRISING DYNAMICS of the hiring market! If you are looking for a job, or looking to hire somebody, reading this might be useful!
http://danluu.com/hiring-lemons/
🦄1
How do you normally autotest an API? You write some custom code or create a Postman collection... But is it a) "the only way" and b) "the best way" of doing it? What if I tell you that you could test your API in the "end-to-end style" and the "unit-test style" (at the same time)!? 🤓 And that you could have ULTIMATE CONTROL over the inner behaviour!
Intrigued?
This article will show you a theory and a practical example of "how to do it".
https://www.linkedin.com/pulse/testing-api-without-e2e-tests-node-express-supertest-example-karaman-uchec
Intrigued?
This article will show you a theory and a practical example of "how to do it".
https://www.linkedin.com/pulse/testing-api-without-e2e-tests-node-express-supertest-example-karaman-uchec
Linkedin
Testing an API without E2E tests?! (Node + Express + Supertest example)
“I haven’t seen it working yet!” Many test automation engineers (and developers) would say that when discussing the test approach for an API. “I haven’t seen it working yet, we need end-to-end tests!” They would say that and make some sarcastic “unit tests…
⚡2👏1
Friday is for good reads! 😎
Here's an article for you called "Being Glue"! https://noidea.dog/glue
This is another one of my favourites of all times! ❤️
TLDR In case you have never seen/read it: "To not harm your career do (mostly) the work that is expected from your role/title"
Here's an article for you called "Being Glue"! https://noidea.dog/glue
This is another one of my favourites of all times! ❤️
TLDR In case you have never seen/read it: "To not harm your career do (mostly) the work that is expected from your role/title"
No Idea Blog
Being Glue — No Idea Blog
Slides and notes for the Being Glue talk.
❤3🔥1
I am on fire this week in terms of writing productivity! So much that I Just published a new article 🔥
It is a practical step-by-step guide on how to make improvements to your test code!
I take a simple API test and do 10 rounds of improvements on it.
What is your opinion, is it better now, same, or worse? 🤔
Fight me in the comments (in a civilized manner, of course) if you don't like it!
https://www.linkedin.com/pulse/practical-step-by-step-guide-improving-your-test-code-ivan-karaman-blhbc/
It is a practical step-by-step guide on how to make improvements to your test code!
I take a simple API test and do 10 rounds of improvements on it.
What is your opinion, is it better now, same, or worse? 🤔
Fight me in the comments (in a civilized manner, of course) if you don't like it!
https://www.linkedin.com/pulse/practical-step-by-step-guide-improving-your-test-code-ivan-karaman-blhbc/
Linkedin
Practical step-by-step guide for improving your test code!
The left part of the screenshot above is an example of the “Todo API test code” created as part of the homework given to one of my students (I coach people on test automation). Can this code be better? How to do it? Let’s find that out! 🤔 This article will…
🔥4👍1🦄1
This is a cool article measuring flakiness of "Cypress vs Playwright".
It might be helpful for you if you are trying to decide on the "next framework to use at work"
TLDR: Playwright is LESS flaky
https://www.linkedin.com/pulse/cypress-vs-playwright-flakiness-analysis-andrew-goldis-kuquc
It might be helpful for you if you are trying to decide on the "next framework to use at work"
TLDR: Playwright is LESS flaky
https://www.linkedin.com/pulse/cypress-vs-playwright-flakiness-analysis-andrew-goldis-kuquc
Linkedin
Cypress vs Playwright - Flakiness Analysis | Andrew Goldis
A data-driven analysis of flakiness Cypress vs Playwright, based on test results reported to Currents dashboard.
👍2🤓1
FRIDAY IS FOR THINKING!
Found cool visualisation on "why accidents happen". Picture is about life in general, so the content quite easily be transferred to the "software development process".
If you slice real cheese and leave it on the plate, all of the big air bubbles will NATURALLY be aligned. If the developer does all the testing, they will MORE LIKELY to create problems (shared cheese bubble)!
If you add other people, aka diversify, you would REDUCE THE LIKELIHOOD of problems:
- another developer doing tests differently (rotate/flip the layer)
- PR review process
- independent testing
- monitoring/observability
- ...etc.
What are your thoughts?
For those with no Twitter/X account, screenshot inside (just in case)
https://twitter.com/sketchplanator/status/1798594426291273963
Found cool visualisation on "why accidents happen". Picture is about life in general, so the content quite easily be transferred to the "software development process".
If you slice real cheese and leave it on the plate, all of the big air bubbles will NATURALLY be aligned. If the developer does all the testing, they will MORE LIKELY to create problems (shared cheese bubble)!
If you add other people, aka diversify, you would REDUCE THE LIKELIHOOD of problems:
- another developer doing tests differently (rotate/flip the layer)
- PR review process
- independent testing
- monitoring/observability
- ...etc.
What are your thoughts?
For those with no Twitter/X account, screenshot inside (just in case)
https://twitter.com/sketchplanator/status/1798594426291273963
X (formerly Twitter)
Sketchplanations (@sketchplanator) on X
The Swiss Cheese Model
The Swiss Cheese Model helps explain why, despite all our best intentions, accidents happen.
You can find this sketch, lovingly polished, in the book Big Ideas Little Pictures.
The Swiss Cheese Model helps explain why, despite all our best intentions, accidents happen.
You can find this sketch, lovingly polished, in the book Big Ideas Little Pictures.
✍1❤1👏1
First real attempt in making short videos after a long break! I got tired of producing "Standard YouTube format" some time ago and was dormant! 😅
What are your thoughts?
https://www.tiktok.com/@ivanandcode/video/7377957578350906642
What are your thoughts?
https://www.tiktok.com/@ivanandcode/video/7377957578350906642
👏2🦄1
Do you want a little challenge?
OF COURSE YOU DO!
I present to you a game called "Petals Around the Rose".
Rules are simple, you need to guess the pattern! This is a good example of exploratory testing: "do -> observe -> conclude -> repeat"
My result will be in comments, feel free to share yours! 😜
(do not google the answer or a game name, it will ruin the fun)
https://mshakerinava.github.io/Petals-Around-the-Rose/
OF COURSE YOU DO!
I present to you a game called "Petals Around the Rose".
Rules are simple, you need to guess the pattern! This is a good example of exploratory testing: "do -> observe -> conclude -> repeat"
My result will be in comments, feel free to share yours! 😜
(do not google the answer or a game name, it will ruin the fun)
https://mshakerinava.github.io/Petals-Around-the-Rose/
🤯2
A little glimpse into the future! 🔮
I have created a course!
It's called: "Minimum Viable JavaScript - programming foundations"
It's not live yet, I plan to release it publicly some time next week.
Main areas are covering the following “howtos”:
- get started
- test your code
- continue learning on your own
And I have a LIMITED AMOUNT of free coupons available (o-la-la!)! So if you are learning JavaScript (or feel like a beginner in it) leave a comment “yassss!!” and I will grant you the wish when it goes live 🧙
I have created a course!
It's called: "Minimum Viable JavaScript - programming foundations"
It's not live yet, I plan to release it publicly some time next week.
Main areas are covering the following “howtos”:
- get started
- test your code
- continue learning on your own
And I have a LIMITED AMOUNT of free coupons available (o-la-la!)! So if you are learning JavaScript (or feel like a beginner in it) leave a comment “yassss!!” and I will grant you the wish when it goes live 🧙
🔥3👏1🤩1