Comments for Catalin Anastasoaie

Comment on 101 test cases for a pen by uilcrw

uilcrw — Fri, 19 Nov 2010 05:50:51 +0000

Something is missing… I know! Background music when reading!

Comment on 10 things NOT to do in software testing by Catalin Anastasoaie

Catalin Anastasoaie — Mon, 15 Nov 2010 05:43:18 +0000

What do you think? For the future I have added a disclaimer just to be sure.

Comment on 10 things NOT to do in software testing by Andrei

Andrei — Mon, 15 Nov 2010 00:49:16 +0000

I hope you are kidding with the 10 things above and this is a post for the Fun/Jokes category on your blog….seriously now!

Comment on 10 things NOT to do in software testing by Catalin Anastasoaie

Catalin Anastasoaie — Sun, 14 Nov 2010 12:45:38 +0000

Even though I’m not allowed to talk to you, I’m gonna say that this is a good one – maybe the 11th

Comment on 10 things NOT to do in software testing by Horia

Horia — Sun, 14 Nov 2010 11:11:26 +0000

don’t question the developer, program manager or product manager. they’re always right. and they WILL take it personally.

Comment on Projects by Billy

Billy — Sat, 13 Nov 2010 20:45:51 +0000

Nice endeavors. Good luck with them!

Comment on “I know it’s late but please help me out guys!” – #EWT17 by Catalin Anastasoaie

Catalin Anastasoaie — Sun, 13 Jun 2010 17:40:45 +0000

Thanks for your comment Thomas, it was a really good assignment with lots of learnings (congrats).

Hope to see you soon, too.

Comment on “I know it’s late but please help me out guys!” – #EWT17 by Thomas Ponnet

Thomas Ponnet — Sun, 13 Jun 2010 17:07:24 +0000

Hi,
I reallly like the thinking that the manager must have looked at the functionality before assigning it to the team. But has he? Looking at the wording he might just heard the name mentioned by someone saying “”That’s a cool compressor, you should use it.”

So the idea is good, if that is then followed up with a quick question about if he actually tested the functionality you’d know that a very large part of the test effort might then be out of scope.

Very good summary, I like the thinking behind it and that you wrote it down.

Hope to see you again soon,

Thomas

Comment on “I know it’s late but please help me out guys!” – #EWT17 by Catalin Anastasoaie

Catalin Anastasoaie — Sat, 12 Jun 2010 19:10:44 +0000

Hi Markus,

Thanks for your comment and for following up on my learning’s. Really appreciated!

Yes, indeed you are perfectly right about the missions and that we must always check back with our stakeholders to see if we got it right or if something has changed in the mean time.

I really hope that we will have the chance to work together again. Thanks one more time for taking the time to comment on this.

Comment on “I know it’s late but please help me out guys!” – #EWT17 by Markus Gärtner

Markus Gärtner — Sat, 12 Jun 2010 18:04:29 +0000

I see a flaw in the first point of your learnings. The problem is that we rarely get clear mission statements. So, we have to formulate them on our own and check back with our stakeholders whether they were correct or not. This has to be done regularly, and over time as projects unfold, these initial missions may also change due to problems being differently perceived, or initial problems being dealt with.

Maybe something to continue thinking about

Happy Testing.