If we already know and understand, different types of software testing, different software testing techniques then what is the need of a section like case studies? Why can't we just follow, already defined processes and best practices? Because.. problems are different, every project is unique, and since we are humans and not machines we are also different. Every tester is unique, in terms of how he or she observes, judges and behaves in a given situation. We are not programmed and our actions are based on a lot of interesting things.

In most cases, effectiveness of our actions is dependent on how much knowledge is behind those actions, what was the thought process before those actions. It can be said that your effectiveness increases with knowledge. Our actions are different, because probably our knowledge level is different. Contextual information about the problem determines our thought process. Effectiveness can be improved if you are aware of more and more interesting problems, domains or contexts.

WOW, Very Geeeky, but lets talk software testing now. This section takes TestingGeek's philosophy of sharing knowledge further by giving you an opportunity to:

• Learn By learning from other people's experience (That's wise :) ).
• Share Your own experience, expertise of testing a specific application, or applying a different software testing approach in the context of application or domain, or automation framework or virtually anything which you feel will add value to other testers. Do not under estimate your work, your challenges, you have a 'TestingGeek' inside you find it out and share your experience with other testers.
• Keep Learning.. Learn from experiences of fellow testers, share your own experience and learning will follow. So 'Geeks' or rather 'TestingGeeks', Keep Learning, as it is an endless journey.

Are you thinking 'How can I share my experiences?'.
Here is TestingGesk's easy Step guide to share your knowledge on TestingGeek.Com.

• Start with the projects you have worked on, software test automation you completed and start writing about it.
• Think of it from the testing interview point of view, what kind of questions any interviewer will ask for example, Describe the application you are working on? What kind of challenges you faced? What were the risks associated? Did you follow any strategy? Can you give us sample test cases? Did you do any software test automation? Were you preparing any matrixes? What kind of skills as a tester you need to test this type of application?
• Tell us some thing about yourself.
• If you are done, send it to

We will publish your experiences, as we feel every experience is worth sharing. If you want to make it more interesting and personal

• You can send your photographs as well and your experience will be published along with your photograph.
• Give us your manager's mail ID, friend' mail ID and we will let them know whenever your article is published.

Your application might fall in any of the domains suggested below. Feel free to suggest TestingGeek new domains, where your application should go as it is not an exhaustive list.