1-Testing — 14 October 2009

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

Related Articles

Share

About Author

(0) Readers Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>