Wednesday, December 26, 2012

Release of my 4th book on software testing

I have released a book each on my mother's birthday followed by my sister's birthday and my birthday. Obviously, my father was feeling left out and I am releasing a book on his birthday. This is my fourth book on software testing.

Book 1: What If... A question every software tester must ask.

When I logged my first bug, I thought – ‘What if’ this bug was found after release? Years passed, many products were released, and I gained a lot of varied experiences.  I made a few embarrassing mistakes too. There were few instances where I wished that someone had warned me beforehand. So, I started preparing a book of tips targeted at software testers. Special care has been taken to keep each of the 22 chapters short and to the point. Emphasis is on ready-to-use tips which would give you instant results.

Book 2: What If... 50+ tips to win testing contests. 

This book is a collection of tips which might help any tester competing in a testing contest. Testers are under tremendous time pressure and the competition is tough. Skilled testers have a better chance of winning the contests. After participating in a number of testing contests, I realized that it is easy to win any contest if you dedicate some time and demonstrate the right skills. In this book, I have tried to highlight few points which will improve your chances of winning the testing contest.

Book 3: What If... 50+ tips to boost your productivity.

This book is a small collection of tips, tricks and list of tools to help boost your productivity. This is entirely based on my experiences in software testing as well as using computer. Internet is so powerful. A simple Google search will yield you so many search results. Google for “Screen Capture Tools” and you will find a minimum of ten tools in the first page itself. Which one do you choose? Do you have the time to try each one of them? What about Windows command prompts? There seems to be more than fifty commands. Which one is useful for us, especially for a software tester?

Book 4: What If... 50+ tips to improve tester-programmer relationship

This book brings into picture a very important person - the programmer & the programming team. Each one of us might have the experience of working with at least one tough programmer. Some programmers are very friendly and help us with finding bugs. Some of them are very strict with their deliverables and do not respond to any queries outside office hours. Some hardly talk to you unless you ask them a question. There are different types of programmers and bring in variety to our testing challenges. As I write this book, I have completed over six years of software testing and interacting with multiple programmers across different projects within and outside the company. With a rich experience of working with tough programmers, I write this book to help you.

My special thanks to my family members (for having a gap between the birthdays), my friends for accepting me as I am, my friends on twitter, facebook who keep encouraging my work, the programmers who keep challenging me, those who bought my first three books, those who provided me feedback and those who continue to believe in me :)
And of course, my love and thanks to my father who continues to encourage me in everything I do.

How to buy the books:
Download from


Vijay said...

Hey Ajay,
Congrats for your 4th book. This brings me great inspiration to publish my first ever software testing ebook.

Keep posting!


Anoop Vashistha said...

Very nice Ajay, good work keep going on.

Monirul Islam said...

I just read 7 tips so far from the book and I couldn't stop myself to give you BIG THANKS for the writings. Excellent.

Tip# 6 reminds me an incident that my manager did to reduce number of 'Reopen' by insulting programmers indirectly. Every time a bug was reopened we put a counter (R1, R2..n) just before the title of the bug. So, it was appearing in the bug list and one could easily understand whose bug is reopening frequently and how bad the fixes were. It was obviously a shameful matter for a programmer when his manager asked why the bug is not closing, why it is reopening so many times.

Not only that we did another thing. When a bug was reopened the title of the bug was changed to red colored. It was another indication that the bug is reopened, it's not closed first time.

Fortunately it worked for our organisation. Developers were more careful while fixing bugs and they did more checks before delivering to test team. However, they were not happy with this decision/changes.

Smruti Sen said...

I just come through your blog while searching more about the software testing. Read your blog and love the way you have implemented the unique content about software testing and other testing related information. Thanks for sharing this and I will wait for your next updates. Keep it up!

Adam said...

Congratulations on publishing your fourth book about software testing. The dates of publication are certainly memorable for you. Software testing is such an important aspect of product development.