Skip to main content


Showing posts from May, 2014

Step away from your PC and communicate "Face-to-Face" !

Over the past few weeks I have grown more and more amused as to how people communicate within the office. You are probably wondering why this isn’t a post related to a test type, a test method or a testing tool but more of a generic post about how we should communicate on projects. This is relevant as a post to a tester’s blog because as we all know testing fits in with the project life cycle.
Long distance communication has become key to the success of many organisations, such as the one I work for with multiple sites and not all based in the UK.
Remote workers and virtual teams are quickly becoming the norm these days, yet sending an instant message or an email is not always the answer. When you meet somebody face-to-face is when work tends to get the job done.
You are now probably wondering where I am going with this? Let me explain…
Ever sent an email regarding a bug to a team of developers? Each of those developers will probably have different ideas about a resolution, right? Emails w…

"Cannot Reproduce" Can We Get Rid Of Persistent Bugs?

Found this article on 10 steps to aid in eliminating those persistent bugs... Thought it many come in useful for some of you testers out there!

Unreproducible bugs can easily make a tester’s existence painful. Too often testers find a bug, then report it and get the answer “This is not a bug – I can’t reproduce it.” Still, the bug may be there, awaiting its next victim. Unreproducible bugs can be very much expensive because of their increased lifetime and investigation time. They may as well have a quite damaging effect on your product perception in case the users reporting such bugs are ignored. Therefore, testers should do better to prevent them. Here are 10 things testers can do to reduce the number of unreproducible bugs even now. Regularly do stress testing of the system unless you want to run across some unexpected failures when it is heavily loaded.Test timeouts. Make tests which fake or mock dependencies for timeout code testing. If the timeout code works wrong, it can cause a bug…