Question Time? Rikard Edgren
There has not been a lot written from us on the blog lately; a lot of other things to do, and blogging isn’t the hottest thing nowadays, to say the least.
Perhaps we also already have written what we feel is most important, and thereby not addressing what is important to other testers.
We therefore open up for questions from you.
Add a comment to this post with any question (although testing related stuff is preferred).
Comments are moderated, and if we have a quick answer it will be posted as a comment.
Things requiring more thought may take time, and end up as a new blog post.
Looking forward to inspiring questions!
I\’m really sad not seeing more content from you, because this is by far one of my favorite blogs – not just QA related, but overall 🙂
I understand you are having a hard time making up the new topics to discuss, but here is an idea – write down some interesting situations/scenarios that happens in your everyday QA work, and write a small article around it. Something happened today? Great, write it down and there\’s a content…. hopefully 🙂
Regards and all the best!
Thanks for the idea, Vilim!
Maybe we could do this, but generally it is much more difficult than one might think.
Of course there happens interesting things almost every day, but one has to give quite a lot of background information about the context to make it understandable, and insteresting. And often one doesn’t want to give so much details about actual work.
But I might give it a try without explaining too much, we’ll see after vacation.
It would be interesting to get a perspective on the software testing aspects now that AI is used widely/vibe coding seems common.
Hi Jenni
Too early to say, in my experience so far the developers only use AI as a sounding board (thanks for that!)
But I have done quite some vibe coding myself for custom tools, often with good results (the simpler, the better).
But, testing gets more important, and more difficult, because almost any kind of bugs can be introduced (problems a real developer never would create)
AI tools can help with unit tests, but both for the tests and the code you need to review what is done.
Exploratory testing gets even more important.
Interesting times ahead, but a fear for more complex product is that development time can be reduced a lot, but testing time will be increased even more.