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’.
|
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? |
![]() @Geek4Eva_ |
@michaelbolton Yes if it is expected to be an ongoing issue. |
|
@Geek4Eva_ And if not? |
![]() @Geek4Eva_ |
@michaelbolton Tricky question. I’d say yes – as thats what regression tests are for. |
![]() @Geek4Eva_ |
@michaelbolton … To prove that already working stuff is not broken. |
|
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 |



Let’s Socialize!