My First Philosophy Post !!!

Hello Everyone,

Hi,this is Chintan Javia and am having an experience of 9 years in QA/Testing area. Across 9 years i have sailed through many domains and experience with working in each domain is thrilling so far. I will share all these testing memories in upcoming articles/post.Excuse for typos and terseness as am from vernacular medium :)

I was thinking to start writing the blog since long but lazy bones resides me always win over my idea to start the blog.But as old saying never say never late.This blog i don't want to limit to testing/QA will write on more wider range.

How QAPhilosophy born?

Don't put so much stress on figuring out why this names, i didn't do much for the same.I was looking for some fancy name and as usual google the savior. Initially i thought it to be some Greek name (Inspiration from my previous project's module name) but somehow its not went well and finally google search won.So this is the story behind the scene on how QAPhilosophy born...

What is My QAPhilosophy?

Generally when its come to QAPhiolosophy, I believe until the work is getting done all is fine.

Few points to consider to become a successful QA :

1.Always try to put attention on business requirement not the requirement stated by BA .Try to break all the so called bugs functional, requirement Gap,UI/GUI,Integration bla bla... in the first cycle itself, it will make your life more easier and everybody will realize this guy will make my go live smooth and you break the ice almost in the first shot.

2.Maintain healthy relationships with all the stack holder Starting from top management to trainee/intern.(This is in a good sense).I personally experienced the benefit of keeping the relationship.... As per the old saying you must be in war with dev with all the time.. I am able to recall the instances where i was stucked or in very pressure situation at client end/offshore and dev team help me to get hell out from there crossing their scope of work.By the way am i die hard tester still...

3.Be it QA engg/QA lead or any damn QA, Once you allocated with any project, try to verify all the aspect and scope and what client expect rather than just falling into the routine activity ---> Writing test Case >> Test Execution >> Defect Logging >> Defect Tracking etc etc...

Things taken into the consideration while jumping into the new project/product...

1.What work has been done and delivered before you entered that magical project/product.
2.What role you are going to play as QA?
3.What difference you are going to create with your injection(Manager's love this)

4.One thing i always see as a difference creator is client communication and i love this.Initially when i was in inception of my QA career i was kind of shy/afraid to face the client but over the years i have learn that i was able to think differently and got so many clear requirement after talking to client only.

Things I have learnt from constantly talking to client are :

1.Got the actual idea about what he require and what he wants us to do.
2.By asking the constant feedback, I was able to rectify the things which he doesn't want in early stage.
3.Able to understand user behavior and how the project/product is going to utilize in that geography.Every geography is having different pattern of accessing the product and you must consider it as one of the key aspect as your testing activity.

Okay folks,This is an end of my first post. Keep watching this space for more updates.
Have a Happy testing till then....