Skip to main content

So how do you Strategize it?

Happened to read Pradeep's blog today and got enthusiastic to write a blog. Found there is a intricate situation for me to blog about, and almost all of us would have faced it some time.

Of late I was called by one of the engagement manager to help one tester (the lone warrior and new joinee to organization) in project to help him on test strategy. Had a meeting in the after noon with project team and got to know that team has least information on project (assignment had begun a week ago). Project is a migration task from one java technology to other and testing activities would involve function testing (with no definition of scope) followed by performance testing. Team is bewildered as they have least information about project whereabouts and the tester has no idea on how he would carry out functional and performance testing. On top of this the very first deliverable for the project is test strategy document.

So our warrior has been asked to come up with test strategy. And he indeed developed a test strategy document on the basis of general info and experience ha has gained over years. The document does not consist any specific attribute to project (for obvious reasons). Now engagement head is not happy with length of document as this is a deliverable which is going to bring more money and probably more business. He believes that it has to have more info. I don't question him for his opinion as his objective is to get more business to company may be right from his perspective.

So what I did? Well first of all I consoled the poor tester who was feeling left out. A new joinee having feelings of not being able to live up to responsibilities of his first job. Besides this only option I could think of was questions, zillions of questions to be asked to client as we had least info about the project. I had a dedicated section added to doc about questionnaire which we had to know before having the testing assignment begun. He added a couple more pointers about exit and entry criteria for each phase of functional and performance testing. The document is sent to supervisor and review comments are awaited.

So what different would you have done in this situation?

Comments

Popular posts from this blog

How to write bad UI automation code (a formal guide)

You might find umpteen resources on learning to write UI automation. But rarely you find any guide on writing bad automation code. Bad automation code is not actually "bad" especially when you consider following - Bad automation code keeps you job safe. Well who can understand the code other than you. Gives you an opportunity to ask for more raise as you are the only one who can maintain the code you write Lets you keep your head up as you the geek of your company who knows that abstruse code  Now coming to writing bad automation code, here are some silver bullets - Record and Replay is the core or writing good (read bad) automation code. It has so many advantages which just out do many others. Biggest being you don't have to write any good code (read bad), tool does it for you. The way to convince decision owners in to enlightening is to let them know that record and replay does not require any special skills. Even your HR can do this.

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

Verify email confirmation using Selenium

Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can