Geek4Eva

Earlier today jut exchanged few messages with Michael Bolton over Twitter. Here is a quick tip from him on when to automate the testing for a ‘broken link’.

@michaelbolton	I told @mhesusser about a broken link on his blog. He fixed it, and tried it. I tried it too. Do we still need an automated check for that? about 8 hours ago from TweetDeck
@Geek4Eva_	@michaelbolton Yes if it is expected to be an ongoing issue. about 9 hours ago from TweetDeck in reply to michaelbolton
@michaelbolton	@Geek4Eva_ And if not? about 8 hours ago from TweetDeck in reply to Geek4Eva_
@Geek4Eva_	@michaelbolton Tricky question. I’d say yes – as thats what regression tests are for. about 8 hours ago from TweetDeck in reply to michaelbolton
@Geek4Eva_	@michaelbolton … To prove that already working stuff is not broken. about 8 hours ago from TweetDeck
@michaelbolton	Here’s what (I say) to ask about in terms of the automated check for broken link issue:1) risk 2) cost 3) value 4) time 5) skill 6) priority about 7 hours ago from TweetDeck

I have been very fortunate to always have had testers with correct software testing skills, either as colleagues or in my team.

Image Source

Matthew in his post on software testing – How do we see ourselves? has reflected on a new tester requesting for some guidance around learning QuickTest Pro.

Hi
I am new to software testing and want help with learning QTP. I am based in (city) and looking for mentor.

Thanks
(name)

Now, I’m not trying to insult anyone. But imagine, for a moment, this appeared on a Carpentry forum:

Hi
I am new to carpentry and want help with learning The Hammer. I am based in Detroit and looking for mentor.

Thanks
Bob The Builder

I would like to make two comments here:

1 – I think he has got the analogy wrong here. If we are comparing testers to carpenters, then the comparison should be as follows:
Tester – to – Carpenter
Tester’s ability of critical thinking and finding bugs – to – Carpenter’s ability of being creative and fixing things in a clean and efficient way
Basic tools: PC, MS-Word, JIRA, other defect logging tools – to – Basic tools: Hammer, Saw, Screwdriver, etc
Specialised tools: QTP, Jmeter – to – Specialised tools: Miter tool, or other such power tools

2 – Therefore, a relatively new tester cannot be expected to always know specialised tools; specially automation tools like QTP. I don’t know the tester in question here, but if he is already into tester (which he seems to be) and is keen to learn automation, then where else is he expected to go for help other than approach some experienced testers around?