IvanAndCode - Test Automation, Testing, and Quality discussions with Ivan
47 subscribers
3 photos
105 links
Curated selection of the materials/news/announcements about Test Automation, Testing, and Quality. Presented to you by Ivan Karaman (aka IvanAndCode)
Download Telegram
A reminder that the "test data generation" livestream is happening today!

...and 2 more streams are in the pipeline!
(link in comments)
🦄3👍1
Surely most of you reading this done some sort of "estimations" in some shape or form.
Then this is a good watch for you. It is not a testing/quality related per se, but useful.

TLDR:
Estimates are waste 🗑

What to use instead? Projections!
Turns out, if you just count "how many stories we have" and "how many we finished" the projection line for the future is pretty accurate (and more agile)!

There's a lot more good wisdom nuggets in it!
Watch the video and show it to your team (and especially your managers)! 😜

https://www.youtube.com/watch?v=QVBlnCTu9Ms
🔥3
VERY NICE mnemonic and visualisation (screenshot inside) for different types of test: UI/Integration/Unit!
The SMURF mnemonic is an easy way to remember the tradeoffs to consider when balancing your test suite:
- Speed
- Maintainability
- Utilization
- Reliability
- Fidelity

Different types (or layers) of tests will look differently on each of those 5 "dimensions"
See screenshot in comments and read full blogpost here: https://testing.googleblog.com/2024/10/smurf-beyond-test-pyramid.html
5
Periodic reminder that "automated tests/checks" should be only part of the bigger picture and testing strategy, not the WHOLE/ONLY THING.

"Automate everything" or "only automation" mentality leads to bad testing.
Bad testing leads to bad product...
Bad product leads to "we need more automated tests"...

...and the circle continues 😅

Sometimes it is worth to stop, look around, and reflect!
https://medium.com/@vrytinki/your-problem-isnt-test-scripts-741adf79bf84
👍2
Really helpful article with a lot of examples on how "glob matching" works. For those who just done a "HUH??" face, this is what is used by many frameworks to search for a certain pattern.
Example use case: need to only run tests that are located in the "/API/" subdirectory

Another example: match that this network call went to the "/users/{id}" endpoint

So it is useful for general understanding + for the users of the test Frameworks like Cypress (author uses cy.intercept() as an example).

Give it a read, picture with a cheat sheet inside!
Kudos to the author - Sebastian Clavijo Suero 👋😎

https://dev.to/sebastianclavijo/unlocking-the-mystery-deciphering-the-enigmatic-code-of-urls-glob-patterns-in-cyintercept-3mgg
🚨GOOD STUFF WARNING!🚨
If you are into test automation & coding, you should definitely bookmark that repo!
This is pure gold! Lots of great testing advice in six categories.
Section 0: The Golden Rule
Section 1: The Test Anatomy
Section 2: Backend
Section 3: Frontend
Section 4: Measuring Tests Effectiveness
Section 5: Continuous Integration

It has JS/Node.js flavour, but lots of the advice will be applicable in other ecosystems as well!

Check it out: https://github.com/goldbergyoni/javascript-testing-best-practices
🔥51
This article is a nice reminder that the bugs are mere symptoms of the underlying issues.

One needs to look beyond the surface of the bug (the "what") to figure out the REAL ISSUE is (the "why")
...and fixing it after finding of course 😂

https://qase.io/blog/bugs-are-symptoms/
1👏1
Did you know that Google Chrome Dev Tools now have an AI assistant built in?
https://developer.chrome.com/docs/devtools/ai-assistance/quickstart

You could ask about:
- networks requests
- performance
- styles

Pretty cool, huh? 🔥😱
Of course, it is a generative AI in its' current state, so you need to take it with a grain of salt. But it will definitely help in some cases, especially if you spend a lot of time in devtools!

(screenshot inside)
🤔2🤯2😎2
I understand that Page Object Model (POM) pattern in test automation is still popular.
But have you ever asked why?
Back when the automation frameworks were doing its' baby steps, chaos emerged.

We needed a way to deal with it. So POM was born.
POM turned chaos into structure

But now... do we need to continue using it?
I tend to think we DO NOT...🥸

Here's a nice article written by Murat Ozcan (and one more link will be in the comments)
https://dev.to/muratkeremozcan/page-objects-vs-functional-helpers-2akj
😎3
Have you ever seen a job ad for a testing position that instead of an extensive list of everything asked for just... time?
Yes, time!

https://www.seek.co.nz/job/82740010
This is a job ad for a game tester position in Auckland, NZ that asks for just:
At least 1000 hours of experience collectively with our games, Path of Exile and Path of Exile 2

How cool is that?! I am impressed!
(screenshot inside in case it will expire)
3😱1
Stumbled upon a potentially useful (to some) website with the:
- small test tools/utilities
- templates
- guidelines

Idea is not new, of course... I guess the main source of value here is that it all is centralized in one place. Kudos to author - Eugene Semenyuk.

https://www.onlytests.io
👍3
Not promoting ISTQB, but found a cool website where one could train and practice the actual exam!

So if you into certificates, check this out: https://prostqb.com/en/study
6
Interesting tool if you are ever doing testing on APIs:

You paste one cURL → it automatically generates 50–200 API tests: boundaries, invalid data, trimming, headers, CORS, enum abuse, etc.


p.s. I haven't really tried it myself, just read some case studies + explored website & github, use at own risk ;)

https://rentgen.io/
🤓21