Exploratory Testing and RedMind

Third dojo was interesting by giving eye refreshing view and we have some fun. I am happy that I can continue my old testing method. Even it have fancy name Exploratory Testing. We found that the ET is what every developer or users do naturally when testing some application. Searching information and trying to find bugs with different inputs and clicks. Inventing the wheel again of course is not purpose and best practices of these inputs can be found from Test Heuristics Cheat Sheet. We use these practices and try to find bugs from web site of University of Turku. We found several validation bugs from forms, language related bugs e.g. hyperlink redirect from page in English to page in Finnish. These bugs aren't showstoppers or neither high priority. But it is good to find these because implementation of validation to form is so easy that now I wonder why these haven't done. Validation expressions can be found from Internet quickly if can't create one by self. You can't make an omelet without breaking eggs.

I must admit that systematical testing is needed even ET is in use. Managers could want report on testing progress and without systematical testing that is quite hard to done. If falling into indiscriminate testing it probably cause some parts those should be tested will be ignored. This could be preventing with manuscript where test orders are thought already.  

We have also nice Redmind overall presentation. These presenters have some hands on experience and I feel they like to use this tool. Redmine seems to be versatile project management web application and development tools can be integrated seamlessly of e.g. version control. Also wiki pages and blogs can be hosted and supports plugins. So if some functionality has not been implemented you can write your own.