TestToTester

Hi All, Thanks to Rob Lambert aka the social tester’s “ 36 days of Web Testing ”. I have put together test ideas I have collected over the years for web testing in a mind map. For now I call it the web test heuristics. I have attached a .pdf version and .mm version of the mind map so if any of you want to add in more test ideas please feel free to do so and share. I would like to thank Rob Lambert, Daily Testing Tips, Santosh Tuppad, Weekend Testing, Joe Strazzere, Josh Poley, The legendary test heuristics cheat sheet by Elisabeth Hendrickson, James Lyndsay, Dale Emery and many others for sharing their test ideas.

Hi All, I share with you all Codecademy & Udacity the two brilliant sites for someone interested to learn programming. What I like about the two sources is that a lot of thought, hard work has gone in to developing the exercises and assignments on them. I have been using Codecademy for close to 5 months now and Udacity for approximately a month and this is what I feel Codecademy: I came across the site Codecademy when I wanted to learn Java Scripting. I do not remember which blog or tweet pointed me to this awesome source but I am extremely thankful to whoever shared the link. The site is extremely easy to understand and I guess it takes just over a minute for you to start typing your first program. I love learning when it’s hands on and less of theory and that is exactly what I found in Codecademy. You read a paragraph and then you code. There are a lot of exercises to practise and a lovely forum to help you around when you get stuck. The site has now introdu...

When reviewing a test case document (now don't ask me if  it was positive or  negative or division or ) I could not stop noticing just how many times the words ‘verify’, ‘check’,’ is displayed’, ‘should be displayed’ is used. A pattern repeats itself which I am tempted to call the “Test Case Syntax” Syntax: verify  << copy acceptance criteria >> is displayed in < > Or verify << copy acceptance criteria >> should be displayed in << copy acceptance criteria >> Or check if << copy acceptance criteria >> is displayed in << copy acceptance criteria >> Check with your test lead to choose one of the formats Example: //Test case to verify forename, surname, post code is displayed in accounts screen   verify the fields forename, surname, post code is displayed in accounts screen This is how intricate development of test cases is. I do not understand why some t...

One of the questions I find hard to answer when I use exploratory test techniques in my project is,”How do you run regression tests? How do you prioritise them? Do you automate them? Do you document regression test cases?” And then a bunch of questions follow. Let me define the context. I work closely with developers; we use either Scrum or Kanban - which ever best suits our project, product owner, business. We do not believe in individual metrics, blame games, stringent processes, and heavy documentation. All we care about is to deliver high quality software. This does not mean that there is no process, metrics or documentation. We have them all, but they are there to meet our needs and to help those who will come onboard to support/maintain the software. Regression Checks At the start of a story, testers pair up with developers to develop feature files using SpecFlow. Some call it Acceptance Test Driven Development and others Behaviour Driven Development [I am yet to figure out the d...

What do you do when you find a bug? Hold on do not answer it right now. Let me first set the context. You are part of an agile team. The developers sit opposite to you. You are testing a feature in a session. You are time bound and have the good habit of capturing notes when you test. When you now find a bug what do you do? Assuming that you have taken enough notes you go on to write a good bug description and may capture a screen shot, video of the bug and continue with your session. At the end of the session do you Open the defect tracking tool (wait for it to load), enter all the fields for a bug, upload necessary evidence and have the tool share the defects with your dev team? Or Open the defect tracking tool (wait for it to load), enter all fields for a bug, upload necessary evidence and then compose an email to the dev team with the bug id’s/descriptions? Or Walk to the developer share your notes; reproduce it if required, work together to identify the problem? I work in ...

In the year 2050 Captain Morgan and his crew are stuck midway development/testing for the next huge OSv5.1 release for their spaceship Jatayu. The problem they are stuck at is: To verify correctness of the results returned from a black box calculator Procedure the crew follows: 1. Answer close to 40 questions [Please note: The questionnaire can have drop down menus, radio buttons, and relationships within questions (some questions will be displayed if a specific question is answered)] The captain of the ship has signed an NDA and cannot share the questions 2. The answers are fed into a Black Box (Calculator) 3. The results are displayed on the screen Assistance offered: Black illusionists have agreed to verify if the values fed into their Black Box are correct or not. But they will check only 25 combinations (we supply inputs to each question and the actual results). They will annihilate us if we exceed the magic figure of 25. Strategies suggested by Problem Squealers in the crew te...

Hi All, Francis Balfe and I will be at the UK Test Management Forum to talk about recent challenges, test strategy and methods which worked for us in our recent project. We hope to get loads of feedback from the audience :) I also look forward to a lot of other great sessions lined up at the forum especially the talk from Mark Crowther. So, if you are a tester in UK and have no plans for the holidays walk into TMF. Cheers