Chronicles Of Testing

Idea generation I have written extensively about Idea generation and the stop criteria here . What triggered me to gamify test idea generation is an environment for testers which was lacking: ~flexibility wrt making changes to the existing test ideas and  ~a lack of training budget for testers. Gamify test idea generation Some of the simplest ways we can learn to test and generate test ideas are: Pair testing with knowledgable testers/mentors Get together to l earn+unlearn Read from blogs and books Tour of the application and sense-making as we take the tour of the product Improvise by role play (white-hat hacker, black-hat hacker, SEO engineer, test for data quality...) Watch a relevant video to gather inspiration The dart game or a  bowl with various testing types and techniques to choose and learn from Tools To Use Note-taking tools Build Heuristics(learn about micro-heuristics) A checklist A mind-map Develop your own Tool KIT...

Establishing the context is essential when conversing, writing and especially when testing. Reasons why establishing the context prior to testing can be missed out: Ignorant or Unaware –Testers/Leaders are not yet aware of the science behind establishing a context. Code and test enthusiasts hastening to verify and validate the product against set requirements. By not encouraging the idea of questioning at every stage of software development, one could dampen the outcome of testing. Relevant and well-timed questioning leads to challenging the status quo and learn new dimensions and the changing contexts that are akin to testing.  Change in requirements requires a change in context, which is seldom accommodated in ardent and uncompromising work cultures. The above scenarios can occur in instances when: The team has not set clear team and individual objectives prior to testing. The code delivered to be tested is delayed and has passed the test execution start ...