Which testing Strategy and Technique will suit you if............

Guys,

What should be best testing Strategy and Technique you refer, if you are given only 3 hours to test a huge project.

I happened to me when I have been given a .Net web (Client and Admin side) based project which includes following major modules along with some basic functionality.

1. E-commerce
2. Social Networking
3. Reporting
4. Forum
5. Blog

They did not use any open source solution for any of the above module and said to me.

"We know you don't have enough time to test even a single module at all, but we want to see bug free deliverable."

I was given SOW (scope of work) document and asked Do you need anything else.........?

If this is the case with you

1. What would be your Testing Strategy?
2. Which Testing Technique will your prefer/use?
3. From where you will start?
4. Will you go for automation?

or simple you will say "I am sorry I can't test it....."

Views: 32

▶ Reply to This

Replies to This Discussion

Permalink Reply by Albert Gareev on December 16, 2009 at 19:05
About what?

Can you go through the question again and point out where it's said that it happened to him [Naveed] when he was an employee of the organization?
Permalink Reply by Joe Strazzere on December 16, 2009 at 20:06
"I happened to me when I have been given a .Net web (Client and Admin side) based project ..."

"They did not use any open source solution for any of the above module and said to me..."

You may still be correct, but as far as I can tell Naveed doesn't mention the word "interview" anywhere.
Permalink Reply by Enrique T. Campita II on December 17, 2009 at 3:47
Or it could be that its a rhetorical question aimed to confirm his original idea or solutions. I usually use that one only to affirm that Im on a right track or that Im in accordance with a group or norm.
Permalink Reply by Enrique T. Campita II on December 17, 2009 at 4:07
3hrs of testing, definitely calls for exploratory testing. acting like the enduser yourself and sending critical issues to developers as soon as possible.
Permalink Reply by Michel Kraaij on December 17, 2009 at 5:37
"acting like the enduser yourself". The enduser isn't actively searching for bugs in the software.

But agreed, focus on possible showstoppers in critical business processes would also be my focus. So probably i would team up with a developer and preferably a business user. The developer for fast bugfixing and the business user for the critical process and charter definition.
Permalink Reply by Enrique T. Campita II on December 17, 2009 at 13:22
Maybe i made that statement unclear. As a client, though its normally the case that client requirements are unclear and would lead to dozens of revisions( "i changed my mind, do this instead....") placing your self on the end users shoes and trying to think like them would make you focus on how the system should act, and therefore, hopefully, provide critical issues fast. Agree its hard to at times to "acting like the enduser yourself"
Permalink Reply by Michel Kraaij on December 18, 2009 at 4:52
Placing yourself on the end users shoes and trying to think like them will make you ASSUME that your focus is on how the system should act". If the user mentions he changed his mind, he/she will probably have a good reason for it. Will this be useless input? Hell no. Will this be fixed within these 3 hours? Probably not.
Permalink Reply by Enrique T. Campita II on December 19, 2009 at 1:26
I guess your right.. enough with the clients point of view and trying to assume you can pick their thoughts or analyze how they want their system to work and just test it as you see it fit.
Permalink Reply by Naveed on December 17, 2009 at 12:42
Well Guys,

Thanks a lot for your valuable comments. I am thinking that it could be more better if i had that kind of guidelines when I was actually facing that situation. :)

And

Albert Gareev, Please go through the complete post before commenting. I had faced that situation in my last job.
Permalink Reply by Albert Gareev on December 17, 2009 at 13:03
Naveed Saleem, let me take my guess back then, and I apologize if you felt uncomfortable with that comment.
So how did you handle this real situation in your last job?
Permalink Reply by Robert Healy on December 22, 2009 at 22:32
Hi Naveed,

Gosh! Sounds fun!

I would start by preparing neat BETA (possibly Alpha?) icons and insisting that on each page one was used alongside a Caveat Emptor!

I'm glad this was at your last job. I hope you never encounter it again.

- Rob
Permalink Reply by Sanjay Kumar on December 28, 2009 at 6:35
Hi Naved,
I can understand your situation, at the same time the pressure also that you are facing as you have a very short dead line to meat the project. I had also faced such situations many times. In such scenarios, below are some of the my personal experiences that i want to share with you.

1. The big advantage for such scenarios is , you have the chance to prove yourself and your capabilities of doing a project under such a great pressure. If such kind of tasks are assigned to you by any of the senior person at your company than you can prove yourself by completing the task.

2. According to me the best possible thing for such kind of testing is note down the areas those are show stoppers. I am drafting some of them according to your modules.

1. E-commerce(assuming its a web based project)
a. The site is able to update the orders placed
b. The site is able to place the orders
c. The payment cycle is working in flow.
d. Valid Order is placed and added to cart or box.
e. The billing gateway is working as required.
2. Social Networking
a. You can look for GUI aspects
b. A person is created , old ones can relogin etc etc

RSS

© 2012   Created by Rosie Sherry.

Badges  |  Report an Issue  |  Terms of Service