𝓝𝓲𝓶

Why didn’t Sauron go after the Ring in The Hobbit when he was in Dol Guldur?
Why didn’t he send his servants to search for it?
And why couldn’t he see through the Ring when Bilbo was wearing it?

I’d truly appreciate your experiences and advice.

So my real questions are:

Can relying on AI for bug reports be harmful in the long run, especially for juniors?

Is it a bad habit if a new tester depends on AI for writing bug reports?

Where should we draw the line?

Should I stop doing this completely since I’m still a junior?

To be clear, I don’t just copy and paste. I always read, review, and understand what the AI writes and if it matches what I described for it before sending anything.

Hi everyone, This is a topic I genuinely want to discuss and get insights on, it's about bug reporting and AI.
Do you think it's a bad thing if I describe a bug to an AI tool (like ChatGPT), let it write the bug report and then send that report to developers?

The two issues they face are not having the rights to The Silmarillion, only the appendices and LOTR, and having to time condense thousands of years so that they don’t have a whole new cast of characters every season other than the elves. And given those restrictions, I think they’re doing great!

there can't be
golden rooms
filled with hate

we must cut
evil out
by the roots

and bring back
rose gardens
and kindness

#tricube #poetry #poem

I completely understand your point!
Very well said ,truly inspiring and helpful.
Thank you so much, you’re absolutely right about everything you mentioned.
And Thanks for the article, I look forward to reading it

No, you’re absolutely right about the message.
Actually, I’m seriously considering using it later when I discuss this matter again.
Thank you very much!

Thank you so much for your help 🙏

How can someone overcome the guilt of buying a book for themselves, the feeling that it's a luxury rather than a necessity, and that the money should be saved for something more useful later on? Especially when there's also the fear that they might not even end up reading it?

For example, if the manager says they don’t want to see a single mistake, what should my response or reaction be in this situation?

Very insightful!
But If we join a project after most of the phases are already completed, and the only new changes being implemented are mostly UI related not logic or new functionalities, does that mean, as a manual tester, I have to test 100% of the website?

yet it's expected to cover 100% of the website

there’s no user stories or documentation to guide the testing. I only receive the Analysis files and Figma design files, Also, I often just dive straight into the website and try to figure things out myself because sometimes there's no user stories or documentation to guide the testing

That kind of pressure makes things more difficult, especially when they frequently point out very small UI issues like slightly off colors or minor visual inconsistencies. It becomes hard to stay focused and know what to prioritize. And What makes it even more challenging is that

Well, i've been told that I’m expected to cover at least 90%of the website maybe that’s a fair expectation when it comes from someone reasonable I'm not really sure,But from management’s side,the expectation is that projects should be100% flawless,especially in terms of UI, even before functionality

Thank you so much for the advice and for your kind words, I truly appreciate your encouragement.
I’ll definitely follow your suggestion and give it a try, I’m curious to see how it goes.
Thanks again, really!

In a real world testing process how is this phrase interpreted and applied!

Since exhaustive testing is impossible what does testing everything in the system actually mean in practice? Does it refer to verifying all functionalities, UI elements, buttons, or does it mean covering every possible user scenario?

Many thanks for your support 💓💓

Thank you so much, I truly appreciate it!

It will add so much value for me, thanks!

Still, I’d love to hear more positive feedback one day.

Since I’m still early in my career and mainly focused on only manual and performance testing, I sometimes wonder if there are issues I missed. I don’t always get direct feedback, but when there are no negative comments after a release that alone gives me a sense of reassurance.

It was one of the best moments I’ve had since I joined the team a few months ago.
I’m the only tester on this project, so even though no one asked how the testing process went, I knew I had done something that's good.

Fixing bugs and seeing them resolved properly also brings a great sense of accomplishment. These are little wins that sometimes keep me motivated to grow in this field. A few days ago, we had a release that went incredibly smoothly, no bugs, no crashes, no UI issues.

Thanks a lot!
One of the most satisfying moments is when a random test scenario comes to my mind, like something involving multiple user roles and responsibilities, and it ends up revealing a real issue. Catching something like that makes me feel like I’m truly adding value.

I'm new to Bluesky, not sure I post about work mind, but I'd really love to join.
I'd like to talk about some of the challenges I’m facing as a junior in testing, to be honest, sometimes I don’t even know if I should continue in this career haha

"I like living. I have sometimes been wildly, despairingly, acutely miserable, racked with sorrow, but through it all I still know quite certainly that just to be alive is a grand thing."
~ Agatha Christie

Summer (1911)
🎨 Nikolay Bogdanov-Belsky