isupport@etifinishingschool.com

Couple of weeks back when I met Pradeep, Manoj and Mohan at Edista Testing Institute, Pradeep handed me a project/assignment report to glance thru and asked for my observations of the report.

I glanced thru the mission statement, test scenarios, bugs logged, testers own analysis/review of the assignment, the answers to the difficult questions like
• What did I do well?
• What did I not do well?
• What wasn’t I able to do?
• Why wasn’t I able to do whatever I couldn’t do?
• How much time did I pit in on daily basis?
• What did I learn about what I don’t know during these days?
• What tools did I use in this project & what tools did I discover?

I felt very happy; I looked for the author name and asked Pradeep for more information about the author and the reply by Pradeep was a “fresher” who has just completed the Finishing school from Edista.

WOW! I doubt if I might have written such a good report as a fresher for my first testing assignment.

Check out the report for yourselves @ http://www.scribd.com/full/13774644?access_key=key-13o6fneq87daonc2luix

From the report I did not see a trainee documenting some stuff for the sake of a certificate or a trainee not interested in testing, forced into the role going thru the formalities of a course. I felt the report is written by a tester, who is passionate about what he is learning that to me is a great sign for Indian testing.

Jai ho etifinishingschool

If you support such an initiative please e-mail to isupport@etifinishingschool.com with Your Name, Your designation, Your organization name, Your web address and ETI would add you to their current list of supporters and publish it in their website.

Comments

Post a Comment

Popular posts from this blog

Exploratory testing, Session based testing, Scripted testing…concertedly

In my last assignment a mix of exploratory, session based and scripted testing helped won an award, appreciation by managers & stake holders at our organization. The quotes from our award certificate “ QA team has come up with some intelligent testing techniques to validate the product. The customer test team was not able to find even a single critical bug after delivery ” Though the award was a small one in terms of the award categories our organization have, it meant a lot to me and the team, because this was the first time the team used exploratory approach. The assignment was not pure exploratory or session based, in fact it was supposed to be scripted, but a mix of all three exploratory, session based and scripted testing helped us learn, enjoy, and meet our mission. The assignment started off with developing test cases. We wrote test cases based on the initial requirement document provided. We did come up with a large number of test cases, of which most were re-written, some ...
Read more

Regression Checks + Regression testing = Regression testing?!

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...
Read more

What do you do when you find a bug?

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 ...
Read more