At funda we believe in testing as a team, @anilkusaksiz wrote this blog why blog.funda.nl/5-reasons-we-b…

test the UI, not E2E systems

Dat is raarrr, dit zou natuurlijk gewoon moeten werken (en dat doet het bij mij ook). Heb je toevallig wat meer info? Dan kunnen we uitzoeken wat er aan de hand is. (browser/heb je er nog steeds last van/iets anders specifieks wat relavant kan zijn)

Funny example: years ago I visited a client, they had their own framework which allowed you to test in 7 browsers on all test environments. They spent a year building it and had 10 test. And those did not run in their CI 🤯

I think it is fun to do and that's why so many people are doing it. I also think that you should not do it.

But it is so fun to do🤣

Nice! Is there already support for multiple environments as well? Would be nice if features branches would go to a separate environment and master/main to the production environment.

- Not able to give concrete examples of skills listed on their resume - Just keep talking and not listening (even after sharing that observation) - Coming in with a list of bugs they found - Us vs. them when talking about developers

0 work items in the sprint? Low commitment/estimation is the best way to always 'make' your sprint.

From reporting it in Jira to write it on a post-it and discuss it in person (however that is a bit difficult lately)

none, I don't like them

Mostly automated, a chatbot called the Panda (we use Bamboo as build server) will let me know when I need to do something myself.

deleting tests

Likeability and critical thinking

don't

Do not hide the pain of testing. Instead let them experience the pain.

I'm trying to get insight in the pain vs. gain of our E2E tests. Last month they found 0 bugs. In the same period the failed for roughly 20% of the releases. Anyone else also measuring this?

A sad story for those people: users are not using your test environment.

yeah 90% of my findings are in the category 'the website did not start at all'

Thanks for your long answer and the podcast. I totally agree on the risk of cheating. However, I think that in a safe environment quality metrics can help teams to make decisions. What I took from this: let's start measuring but without explicit goals