Side effect of working in Moolya

We do a lot of work with mind maps. Our test strategy, test ideas, session based test management, exploratory testing and what not. Working with mind maps is so cool. Our testers seem to take it outside of just work. Mohan Raj has been working with us for close to half a dozen months and relocated to Bangalore from Pondicherry. When he relocated here, he found his relative running a hotel in Bangalore and probably observed how difficult the menu was to read and quickly locate what people want to.

He did this amazing thing. See it to believe it.

 

 

hotel menu mindmap from a tester from moolya

 

Mohan Raj had not told any of us in Moolya about this. When Dhanasekar happened to visit the hotel, he was surprised to see the mindmap menu. He took a snap of it and discovered Mohan Raj helped the hotel with the mind map menu. DS shared it with me and I thought it is wonderful to let the world know the side effect of working in Moolya. Cool work Mohan Raj.

 

Moolya got its first CEO and third co-founder

Yeah, it is time we announce that we have a new CEO, our first official one. I was playing multiple roles over the last year and three months from being a janitor (when needed) to tester to recruiter to consultant to finance to MD to CEO. Although I might done reasonably well, Moolya needed a specialist CEO. It wasn’t actually hard to find the specialist.

Introducing to you, Mohan SK Panguluri (a.k.a PSK ) , our CEO and the third co-founder. We were tight lipped all this while and it was kind of hard. Mohan and I have been working together since 2007 and he has been extremely impressive at work and the way he has picked up golf. In his previous stint, he co-founded Edista Testing Institute, serving as its COO and facilitated the growth to a million dollar organization. He has a bachelor degree in from BITS, Pilani and Masters in Business Administration from ICFAI. Prior to ETI, he was with Tata Consultancy Services in the United Kingdom heading a specific sector of business, Zee Telefilms and Planetasia. Prior to that he has played several roles of being a web designer to brand manager and things that today is helping him be a cool CEO.

Mohan has a wonderful family. He is married and has two wonderful daughters who keep his wife dancing to their tunes. That said his wife, Harini is a dancer by profession. Mohan’s parents live with him and in the same house, making it a dream family of today’s India.

The big question is, how is he the third co-founder of Moolya?

The decision to start Moolya was done by me and Santhosh in consultation with Mohan. The name Moolya was decided on August 26, 2010, sitting in Mohan’s home sifting through options and sipping whisky all through. He was consulting me on strategy and decisions ever since the birth of Moolya and has been a part of all Moolya events. He believes in Moolya so much that he decided to be in Moolya full time amidst 10 other options and investors waiting to invest on the ideas he had. So, that clearly indicates why he is a part of Moolya. Oh by the way, Test Republic was his brain child which is now India’s largest online community for testers.

Mohan has had a great influence on me and Santhosh. As a matter of fact, Mohan magically brought Santhosh to me and vice versa. So, we are here as the board of Directors with the leadership shared between us and most importantly playing roles that we most suit in.

Mohan plays golf (as every other popular cool CEO does /at least in movies/) and is slowly (rapidly) getting me infectious to it.

What does this change for Moolya?

I am a hardcore passionate tester who learnt how to deal with business. So, I am not as good at it as I would be in testing, consulting or coaching. Mohan is a hardcore passionate businessman. That means, he would be as good as I am in testing, in business. Ever since he came in, we have seen quick cool changes. I admit, I am amazed at how many things I didn’t do over the last year just by watching Mohan in action over the last couple of weeks.

He got a lot of things done and our employees have visibility into a lot of things. We were confused over policies for organizations and he sorted it out like breeze. Things are now moving fast, we have faster and structured mechanisms to handle the “business” part of testing.

Mohan shall help Moolya’s business grow huge, achieve scale, handle operations, co-own strategy with me, handle finance and oversee we reach business targets (and put the hot iron rod when required :P )

What does this mean to me (which indirectly means to Moolya)

Actually, this is what I personally think as a redefining moment for me and my career. To me, this means, I am back into testing. Hurrah! Dear Michael Bolton and Vipul Kocher, you were right – running a testing business would definitely keep one away from testing. Dhanasekar would know that I have cried many times over the last year and half that I am unable to test as much as I would love to.

Now, my role is to test and consult for projects that Moolya gets. My hands (err, brains) would be in every project. I will head the overall delivery for Moolya. I will work more closely with people I want to work and mentor testers. I will sit beside testers giving them a tough time or asking me to give a tough time in testing things whilst doing all that with good intention to help them do better. I shall also handle pre-sales work (so that we don’t make some claim that we can’t live up to) and consult / coach for Moolya’s clients.

I went for a vacation that I had not taken over the last 2 years, about a week ago. It was so beautiful. My personal thanks to Mohan, without him, it wouldn’t have been possible.

Mohan sometimes felt left out in the action happening at Moolya. So, he picks up a project we are testing, tests and send a test report to me whenever he finds time for it. Perfect. We have a CEO who tests. That must be Moolya. I shall mentor him to test well. That must be Pradeep :P

Note that Moolya is young and highly energetic. We will rise big and good that we will make ourselves and you proud of what we have achieved in testing. That shall be the aim.

In the coming days

You will see plenty of action. Lot of innovation in testing. Crazy ideas being floated. Lot of interesting people coming into Moolya and customers loving our relationship.

All customers we started to work with an year back have given us repeat business. We are talking about at least a couple of multi billion, couple of multi million and a couple of startups. Now, there is an awesome pipeline, impressive track record and too good goals. Beat that!

The testing community support for Moolya has been the most impressive you will ever see that happened to any testing startup. We owe you folks a lot. We won’t disappoint you. More hot and cool announcements coming soon.

Please join me in officially welcoming Mohan (a.k.a PSK) to his own company, Moolya (and congratulate me to starting my second stint as a tester)

Moolya FTW!

Test Mobile applications with COP (who) FLUNG GUN

 

User scenarios and Functionality may be the major theme while testing any software. Software generally comes withdetailed help file. Complex and unfamiliar workflows later become a standard. But the trend is changing in mobile world with minimal help file, and more intuitive ways of interacting with software with minimal learning curve. Mobile users use applications on the go, so network availability and data consumption plays a major factor while testing. So, there are several factors to test for in Touch devices.

This mnemonic COP FLUNG GUN is to remind testers of what to think about when they are creating tests. This is inspired from James Bach’s SFDPOT (San Francisco Depot) and Jonathan Kohl’s I SLICED UP FUN!

Communication

People may use smart phones for different reasons, but the primary task of the phone is to receive and make voice calls. How does your app behave on interruptions during incoming calls? How does your app communicate with voice call, texting, and voice messages? How easy is it to attend, reject, hold, or disconnect a call while using your application? Test the app not just on Wi-Fi, but also with good cellular connection with constant interruptions and noises.

Orientation

People can rotate mobile devices at any time for various reasons. Whatever their reason for rotating the device, people expect the app to maintain focus on basic functionality. Do you test changing the orientation in a sign up page of the app? While on a pop up screen? With notifications? With touch keyboard on? While filling a form? Do you change orientation and scroll, swipe between pages, pinch zoom? Does the app change its size and alignment as per orientation? If the app is not designed to change its orientation, are people informed? Never test mobile applications keeping it static at your desk, carry them to the pantry, to rest rooms, use it while traveling, on your bed, lying on a couch. Apart from observing orientation, also look for ergonomic related tests and clues.

Platform

One of the ways to understand the platform is to explore, observe and learn platform’s standard apps. Apart from those, track and use most popular and most downloaded apps like Zyte, flipboard, Instagram and games like Temple Run, Draw something. These apps will help in knowing various gestures, how certain gestures can help users accomplish a task with ease. These apps will help compare usability, and user experience of the apps under test.

When it comes to Apple you have to think different, apple thinks different and set a trend, and rewrite the rules. So, the heuristics like similar products can’t be applied here. So, how to test such new paradigm shift? To test Apple products you should be a fan of Apple, a true apple fan, else you would never understand why things are done certain way. Apple focuses on getting better ways for people to interact with software; it never wants users to worry about internal file system.

Though heuristics and mindset need change, the core skill to test remains the observation skills. Observation starts even before you open application, even before you power on your iDevices. Have you observed the way people carry their iPads? Covered with neat leather case makes them look as if they are real paper notebook. Have you ever observed how people take notes in iPad? Do they click on new file? Click on save? Search in a folder to open xxx.TXT file? You click, now tap notes app icon, type your notes, once done close as if you were taking notes with a pen. Apple never wants end users to learn all technical details to take simple notes. Apple restricts end users from accessing the core OS file system, but for good.

Android, most tech savvy people embrace android mainly because it is an open platform, not restricting users from accessing the OS. Users here expect every app to behave the way they love when they change their settings. Do you derive tests by discussing with tech savvy android users? Do you test with unrooted phones? There are many different display resolutions, OS versions available; it’s good to have a combination matrix to cover most popular screen size and resolution variables. Though there are simulators, they would fail on real device. One recent example is the Temple Run game failure on many android models.

Function

Everything that a product does, the most common form of testing, for the requirements.  See that each function does what it’s supposed to do and not what it isn’t supposed to do. Starting, shutting down of the apps, interactions, multimedia, file access, navigation, user interface, data syncing on the cloud etc. Did you tap all known interfaces? Did you enter all possible data in the form? Did you change the settings?

Location

Location tracking is one of the key features to be tested in mobile applications. Unlike desktop devices, mobile devices are mostly on the move. Geo location tracking: Most of the apps these days have the feature to track your location, how easy is it for people to change the settings? Are people informed clearly about their location tracking?  Does your application adhere to mobile platforms location tracking and other privacy guidelines? Moving from one location to another location how is the application behavior when moved out of Wi-Fi connection? Moved from one data network to another? Never test mobile applications sitting in one place.

User Scenarios

It’s about thinking real scenarios of how a mobile device and the application would be used by people.  Try to think of how a tech savvy user would try to accomplish a task. Think how a novice user who never had a smart phone would try to accomplish a task. Try credible, complex user scenarios. List out possible users, environments, commonly used scenarios, extreme scenarios, disfavored scenarios.

Network

Mobile applications are mostly used on the move, and so depend on availability, strength and reliability of Wi-Fi and cellular networks. How does the application respond while moving between Wi-Fi, GPRS and 3G? Does your application automatically use Wi-Fi when available instead of cellular network?

Gestures

In this part of world, apps respond to gestures not clicks. People expect all the gestures to work the same, irrespective of apps. Does your application respond to gestures? Navigations are by swiping on the screen, no more, next and back buttons? are people indicated properly that there is more than one page available to swipe? Does your application respond to various multi touch gestures? Does your application use standard gestures? Are the gestures consistent across the app?

Guidelines

Most mobile platforms have guidelines for developing app, Apple has iOS Human Interface Guideline (HIG) and Android has Design. These guidelines will help to build standard gestures, icons, and menus in a specific platform.

There are guidelines for app store approvals like Apple’s App Store Review guidelines. Use these guidelines to test for error handling, location tracking, user privacy, accessibility, logging etc. There could be important changes in guidelines, which need to be tracked and tested for changes, like Apple restricting apps from accessing UDID to identify users.

Updates

Another important factor to consider in mobile platform, unlike desktops the updates here are frequent. While testing, it’s always good to start with at least one version lower than latest, use the app, now upgrade to the latest available version, and observe the application behavior.  Updates also need to be tracked to learn about new features available to app developers, and how that could change the workflow or existing gestures. Good to have app developer licenses of various platforms and explore the developer beta seeds to get to know all latest features.

Notifications

Notifications enable an application to inform its users that it has something for them. How does your application use notifications? How easy is to turn on\off your app from notifications? Does your application use local or push notifications? Notifications in iOS are delivered via Wi-Fi only if there are no cellular networks. How does your application behave if device is in sleep mode? How are the local notifications displayed if screen is locked? Does the app provide too many notifications? Test for all available types of visual notifications, sound and vibration.

How does your application behave during notifications from other applications? Test your application with all possible notifications from different apps enabled. Does your application continue to function properly after clearing notifications?

I start by measuring how quick I could accomplish a task that an app is intended for. The measure is both in terms of time and number of taps. No user want to spend more than a minute in a mobile device to perform basic tasks on any app.  Then move on to test more complex tasks, change setting, move between different networks, different gestures then other mnemonic. But this is just a start, don’t restrict yourself to being a steward of received wisdom; be the author of your own wisdom” from Lesson 47 of “Lessons Learned Software Testing” book.

† – Thanks to Parimala Shankaraiah for helping to form COP FLUNG GUN mnemonic.

 

 

The myth with good & wannabe good testers in India about Moolya

Isn’t it awesome. Some (from the ones we know) good testers in India (good according to us) and some who are wannabe good testers (wannabe according to them) want to join Moolya. As a matter of fact Moolya is their dream company.

When we were actually feeling proud to have created a company which has testers dreaming to be a part of it, the same people who made us happy are kinda disappointing us with a myth they appear to have and thankfully communicated it to us. I personally got irked to hear the myth. The myth they have is — they are not yet ready to be a part of Moolya because they aren’t awesome yet.

These testers follow Moolya everywhere. They would read a blog post within minutes of publishing, follow our testers on Twitter and Facebook. All that is great folks, when you are doing all that, why don’t you come in and experience Moolya? Ah! No! You are not awesome yet? Hmm!

 

Dear folks,

The entry criteria is passion for testing, which you have. The entry criteria is, you are willing to work hard, acquire skills and also demonstrate what you have been doing all this while. The other easier entry criteria is, we know you and you know us. The most important is – you believe in Moolya.

I can tell you that finding people like you is hard and now that you are showing interest to join, it would work out well for both of us. The thought you have about “first be awesome and only then join Moolya” is a myth according to us. We are actually extremely happy that you are thinking that way, however, our future bets depends on people like you. If you are staying away from us, our bets are not going to work and slowly Moolya is going to lose this charm that it has today and it will end up becoming a company that you were happy you did not join. So, Moolya’s future is not only decided by people already working in it but people who are deciding to join it but not doing it. Ah, I mean, not everybody, but people who matter.

Moreover, you get more good by being with more good people. Having understood that is why we want to welcome you on board this journey. Fortunately, there are so many good things to learn and we haven’t learnt that all. We have a lot to learn and you could help us with your knowledge and skills and we could help you with ours and constantly keep growing it. We will continue to add good people like you and make the learning experience stronger.

Some projects we have demand for more good people and if we bring in anybody who doesn’t match to our thinking, we would end up losing the work. So, Moolya needs you as much as you need Moolya.  For exploratory testing, scale is a challenge. Moolya is a company who is going to be an answer to it but if you don’t jump in, the world is not going to.

Look at Dhanasekar, Sunil, Parimala for instance. They were interested to work with Moolya and make it their own and Moolya was also interested to make these people its own. You are free to write to these people and ask how is it to be in Moolya? If Pradeep had decided to first learn how to write good blog posts and only then wanted to start blogging, he wouldn’t have started blogging at all. Excellence is about refining and not about defining.

You may or may not be surprised to know that as of today Moolya has about 20+ testers. The time is now, dear fellas. I am awaiting your email about your notice period and a possible date you want to come over.

If you want to be awesome and only then be a part of Moolya, then you don’t know what awesome really means or you don’t know how to achieve that.

However, if “being awesome first” is not a reason but the truth is something else, learn to speak the truth. After all, you are testers who are supposed to be speaking truth and even paid for it.

The time is now!

A note to those who are not in the list of people we know but still want to join us: The time is now! Especially, the people whom we know and are good don’t seem to be making a decision and giving you the opportunity and time.

Looking forward to your test reports and profile at careers@moolya.com

An interview with Dhanasekar Subramaniam : 1 year @ Moolya

Someone who believed in Moolya right from first communication about Moolya is Dhanasekar (DS as we call him in Moolya). He has done stuff that only passionate and skilled people could have and we are excited to be working with him. I personally have enjoyed the company and work of DS.

While people of his age were worrying about how to be ahead of rate race-iness thing, DS leaped to chase his dream of being a part of a future that could redefine testing in India (and then maybe the world). Moolya is very strong because of people like DS. He has worked on at least 2 big projects a couple of small projects so far.

He played a Lead role for testing a legacy system where people had no clue about it and it looked like a maze. DS went through some tough times to get things going in shape for a project. He was able to influence people around him to change for the good and I consider that a rare skill from a tester.

Oh, I must talk about his mind mapping skill. He is fundoo. I was having a call with a potential client who asked us if we could give a mind map of our understanding of their product. DS put a mind map that our potential client is on the way to become a client.  His passion seemed to be towards testing Apple, touch devices, smart phones, tablets and applications that run on them. We got a client who wants to be a leader in a specific market for mobile applications. DS played a Lead role in it and did “awesomeness” that our client said two cool things:

“Is it common that you find so many bugs or our product is a little extra buggy?” and “We love working with Dhanasekar, he doesn’t beat around the bush, communicates directly and is focused”

DS did a couple of cool things. He helped people in different business functions adopt mindmaps for reporting and communication. Moolya needed someone to be a technical head for our mobile testing division and thankfully, we didn’t have to look too far. DS is now equipped with a Macbook Pro, iPad and a Windows Phone. He was able to coach testers for testing mobile applications and do it on par with the kind of quality of work we want to maintain. DS introduced Exploratory Testing and Session Based Test Management to our clients and to some of our testers. Here is my interview with him on the occasion that he completes one year with us:

PS: You complete one year at Moolya. How is that feeling for you?

DS: Awesomeness!!!

PS: You have seen Moolya grow and continuing to grow, what do you think is the secret ingredient (ha ha) for Moolya do it? 

DS: Passion, Honesty and Self-belief.

PS:  What would you call as your personal accomplishments in the last one year at Moolya?

DS: Whatever accomplished could not be called personal other than remaining a bachelor: P. I take pride in building Moolya’s capabilities on mind-maps and mobile testing.

PS: What did you expect when you joined Moolya last year this time? How much of your expectations are met?

DS: I didn’t join with expectation of getting something at end of every year. Moolya was started with mission to provide value to customers and testers, and I think Moolya is providing it consistently.

PS: What were some of the “awesome” moments for you here at Moolya?

DS: It started much before I joined Moolya, the day you told me about starting your own company, office inauguration pooja, our first client, our first MNC client, seeing our mind-maps about product coverage in developers desk at our client location. These are apart from the ones we had in and around JP Nagar garden restaurants ;-)

PS:  How have you benefited by the people you worked with at Moolya?

DS: Choose the world that supports you. Moolya is a definitely such a wonderful place filled with testing brains and hearts :) . Though I know all of them even before joining Moolya, working close with them has provided wonderful opportunities to observe a lot from them. Parimala : How to manage people and project.  Sunil : How to remain calm and get things done even during chaos. ST : How to mix fun and work ;-) . PS : How to interact, communicate, anticipate and present exactly what a target audience or client would need.

PS: You were promoted as the Commander of Mobile Testing this year. What does that mean to you?

DS: More responsibilities, more challenge and more opportunities. The new generation mobile hardwares are as powerful as desktops and laptops. Apple is embracing iOS and bringing many of its features to Mac OS X. So, this division would play a vital role in Moolya’s future, and help Moolya to reach new heights. The testing style and context here is different from  a typical desktop or web application testing. For example, the general expectation in desktop application is to have detailed help file, but in mobile device it should be very minimal, this mean there should be change in mindset. So, my role is to help testers to get the right mindset while testing mobile applications.

PS: How are you going to change the world being in Moolya?

DS: Toughest question :) I escape saying “I rely on Moolya for this” ;-) Honestly, I don’t have an answer for this right now.

PS:   I personally think you are the master when it comes to mind mapping for software testers, how did you pick that skill?

It is love at first site ;-) .

The pictorial radical arrangement of mindmap got immediate attention from my brain, it said “wow! I can easily associated such representation of information”. From then I started using mind-maps where ever possible, both in testing and personal life. I would like to reveal a secret ingredient here(ha..ha..), if I run out of ideas while creating mind maps, would start changing the fonts, colors, layout of nodes that helps to take a small break in-between, its perfect blend of art and thinking. The only rule in mindmap is “There are no rules” :) , there is neither right nor wrong way of creating mindmap. Anyone who realize mindmaps are captured for her own reference can easily master the art of mind mapping.

PS:  We know you are a great fan of AR Rahman and Apple. How has being a fan of the two great A’s helped you at work?

In AR Rahman and Apple, I see lot of similarities. Intense focus on what they do, giving importance to every minute details, never compromise on quality and consistency in maintaining it.

When I multitask, I felt I was never effective. I even felt it’s my negative looking at many who does multitasking (or pretend :-) ). From AR Rahman I learnt that he doesn’t multitask, instead when he focus it’s intense on one task. According to him focusing is a spiritual thing, nothing comes without losing something and you can’t have everything. After that I never felt it’s a negative instead started doing one task at a time with intense focus. Another quality I would love to inherit from Rahman is his humbleness.

Apple always reminds me quality and simplicity. A rare company, which never compromise on quality for anything. Being a tester Apple always reminds a benchmark for quality, being an Apple fan helped me to test the new generation multi touch mobile platforms with ease and passion.

PS: Give us a couple of testing challenges that you can solve now which you could not have an year back?

DS: Mission focused testing, test coverage tracking using mind maps are the skills I developed in past one year, through the opportunities and freedom provided  by Moolya.

PS:  What is your advice to people coming in to Moolya in future?

DS: Pursue your passion. What matters most is how you look into things.

PS: What’s your advice to Moolya?

Remain Moolya :)

PS:  What do you plan to accomplish in your 2nd year at Moolya?

Twice the awesomeness!!!

To find out what twice the awesomeness means, stay tuned. 

 _end of interview_

A small note to you DS (and probably to others): Time isn’t a milestone, your work and its usefulness to the world is.

 

A valentine’s day letter from testers to programmers

Dear Programmers,

Greetings!

Hope you folks are doing great. We testers wish you for the season and for a great valentine’s day.  Somehow, we are made to look like enemies of each other although we are working towards the same goal. At times we bring our personal ego into a project and make you think we are a bunch of stupids delaying the progress. While some of us are real stupids, not all of us are. I guess, if you are a passionate programmer, you would be irked to come across a bad programmer and that is the same way we feel about testers who bring their personal ego to the table when having to work closely with you. Based on our experience, we seem to have equal good and bad people each sides.

On this day, called valentine’s day, marked to show the love, we want to write this letter to you. We want to tell you that we don’t hate you, there are some of us who love what you do. We have high appreciation of what you do. There are plenty of software we use and it works great deal and solves plenty of our problems, of course without creating new ones. So, we are thankful to the community of programmers. Although some of us don’t publicly acknowledge this, which is sad, we actually do appreciate what you have done for the world and what you will be doing.

The part that I personally feel great about you programmers is – you are patient about the poor bug reports we write. Some of us, write bug reports so bad that the good bunch among us can’t tolerate one bit. Wondering how do you not punch us when you see we reporting a spelling mistake with tons of spelling mistakes in our report. The way you hit us though is uber cool. You actually don’t associate credibility to such testers and that is definitely a way we encourage you to do. Only the skilled should gain respect. Only those who want to grow skilled should be encouraged.

It also amazes us when we see some among you getting excited about the bugs we report and enjoy fixing them. We have personally worked with a few programmers who said, “it was an awesome learning trying to fix this bug. Thank you”. I guess the “Thank You!” is something we should use often with each other. Our work revolves around you and your work revolves around us. That reminds us that both of our work revolves around some other stakeholders.

Isn’t it amazing that some people who claim to manage us, set metrics that makes us to compete against each other than working with each other. I think we should partner with you and fight against people who are dividing us. At one end they put a metric to us on “How many bugs we found?” and at your side, “How many bugs did your code not have?”. Sad. So sad that we need to get out of this soon. I guess if we partner better, we can weed off many of the stupid metrics in our industry.

We testers sometime seek inspiration and encouragement from you, dear programmers. I am sure the vice versa is true. Most often we don’t come to your desk and tell you, “I think you did this part great”. How sad, again. I think we should do it more often. I think it is so important for us to tell you what things went great. At times we feel intimidated by what you speak. You actually let us know what we should be knowing. Those among us who catch it, pick it up and learn and those who hated being intimidated try to stay away from you or get used to intimidation. Sad, isn’t it.

Speaking of that, some groups of testers think that testing is about finding problems in your work. We request you to not bother about them because we ourselves ignore such people. They would never do good testing. They are the ones who balance out the bad of your group.

It is so weird that sometimes we have fought about a bug we reported not being fixed and wasted several hours on it while the fix actually takes a few minutes. We hope to not waste your time and ours in future with those silly fights. We better move on and meet our goal of finding other quality related information.

Unfortunately, our good test education isn’t being able to outnumber the bad test education that is already wide spread. Mostly because businessmen is always wanting to scale quickly and make some quick buck. They act as though they know when they are going to die and want to make money today itself.

Someday, we are hoping we will have a generation of businessmen who are futuristic thinkers and who will actually live beyond their actual life times. That day, hopefully so many of these problems will be solved.

Oh my! We haven’t been calling you as “developers” in this letter. Not that we hate the word but we feel that everyone of us develops. We develop test ideas while you develop product. You program, we test. We love your great work and we are sure you love our great work.

Today, we take oath on the following things:

  • We will let you know what we like about your work, more often than what we might be doing now.
  • We will help you see our rationale than bringing our ego to the discussion table.
  • We will work hard towards changing the perspective that testing is about finding problems with programmers work and help people see that we provide quality related information to different stakeholders.
We are cognizant that you reciprocate action than words. We are hoping that our love for each other becomes an example to other industries on how two different groups with same common objective should work. Yes, we can.

With Love,

Testers

At least at Moolya

Software Testing Resume, Job Application & Test Report Bloopers

We announced hiring 10 good testers on Naukri , one of India’s largest job search portal. We got more than 6000 applications to our careers mail id over the last month. We are overwhelmed with the response and interest people have to our posting.

We want to bring out some of the bloopers from the responses we have received so far. We also want to help people on what impact such bloopers have on considering people for interview or hiring them. If any Moolya testers looking out for a job and reading this ( :P ) please ensure you avoid such mistakes. It creates a bad impression on the organization that has hired and retained you if you do such mistakes. The following are some of the many hundreds of bloopers that is on top of my mind from what I saw and experienced.

Covering letter bloopers (just some of them)

  • “I will be waiting to here from you” / where? here? /
  • “Kindly update my resume” /We should update your resume?/
  • “Dear Hi” /wow, never heard of Dear Hi/
  • “plz,kindly considering me,i m joining in ur company as much as u want.” /head spins/
  • “Notice Period – 30 days but I can join in 15 days and if really urgent I can join in 10 days” /period/
  • “ By virtue of my ability, knowledge and qualifications, I am looking for a suitable job” /virtue leads to job search?/
  • “If you have testing opening find my testing profile and if you have development work find my development profile” /smart in unnecessary proportions/
  • “i like to have a head-on interview at your convenience” /head-on?/
  • “please Find the attached Resumeaa” /wHy cApitalize?/
  • “Please ignore my previous mail.” /we did, including this one/
  • “with referance to ur mail, i here by attached my cv……….” /please refer to dictionary for reference/
  • “Kindly forward this to your company and schedule an interview with me” / :) /
  • “I have enfolded my resume along wit this mail. pls, have a view on it.” /enfolded? /
  • “Hi, I need 30% hike” / great, why not 50%?/
  • “i am attching my updated cv for testing position” / also please update your vocabulary /
  • “Hi dis is XXXXX. Have attached ma cv along” / K, ma cmpny dsnt hyr ppl lyk u/
  • “If my resume for your requirements please let me know” /and the sentence completes after…/
  • “I am interested get this opportunity” /sure, why not? get it/
  • “ I have learnt certain values such as integrity and respect for people and swear by them now” / dizzy /
  • “Please find out my updated profile” /ok, how do we find it?/
  • “I am attaching my upgraded resume please help me out ” /upgraded with what?/
  • “i know bug traking tolls bugzilla” /yes, you know bugzilla but how would you report spelling mistakes in it?/
  • “Please” (just that in the mail) /excuse me/
  • “Am i sending my resume plz kindly go through it” /are you sending?/
  • “Notice Period:15days,I’m Ready to join in an 2 weeks.” / wow, 2 weeks not equals 15 days, it is 14, great/
  • “Please attach my resume” /sure, if I have yours, I will try/
  • Also please check my LinkedIn profile with this link http://www.linkedin.com/profile” / oh man, that link? /
  • “Kindle find attachment” /Amazonnnn /
  • “Notice period is 20 dais” /How can anyone in the world get spelling of ‘days’ wrong?/
  • “Hire me please” /So desperate?/
Resume Bloopers (again, just some of them)
  • “exxcellent in documentation skills” /this is like telling, “I no inglish grammer/
  • 12 pages resume /sorry, we didn’t ask for autobiography/
  • Clients my companies work for /Hey Ram! That list must be confidential/
  • Project description of one page with so much of confidential information /Wow, you forgot the NDA?/
  • “I worked for Google as a tester and they paid me XXXX as salary”… snip … end of resume: “Client Google Parent company: XXXX” /If you are not proud of your parent company but take more pride about the client you worked for, you probably would do the same to us. /
  • Career objective /Most of them are copy paste. Most don’t appear to have a real career objective/
  • /Personal details: PAN Card number: XXXX XXX XXXX / ( Why would anyone need that to interview you?)
  • “mannual testing” /Wow, that’s new to us/
Interview Bloopers
  • A guy walks in to interview just after a heavy dose of Pan Paraag and it takes a while for us to get the Pan Paraag smell out of our office. It would be hard for people to work with such Pan Paraag addicts and we recognize that they paint the wall red :)
  • “Moolya: So, why are you wanting to move out of your current organization? Candidate: The company is closing down. Us: Really? We heard a news they got funded recently. Candidate: Well, uh, hmmm, well, ….”
  • “Moolya: What do you know about our company? Candidate: This company is into helping children in their education. Us: Anything else? Candidate: No” /Just having read one blog post?/
  • “Moolya: What kinda websites on software testing do you refer? Candidate: Google.com Bing.com” /Yes, yes, agreed/
  • “Moolya: You say you have done usability testing but your resume is full of red and green. Candidate: Sorry, I keep spelling and grammar check disabled to type fast.”
  • Some candidates don’t turn up for the scheduled interview. We even come on Saturday’s to make it flexible for some candidates to attend interviews but if they don’t turn up and bother to inform us, we black list. We think there should be such global black list.
  • Some candidate, “I was fired” : Pradeep: “Wow, me too. I am open to hiring people who were fired but curious to know what happened” Candidate: “My manager is an ass hole” Pradeep: “Hmmm” Candidate: “He didn’t give good hike to me so I yelled at him” /Jesus, I wish he had told, “He didn’t allow me to run the tests I wanted to” Marked as Red/
  • Shaking hands after having come out of the washroom and still having the wet on your palms is a little irritating.
Test Report Bloopers
  • “I can’t share my test report because my company doesn’t allow that” /Good but where did we ask you to do that?/
  • “Please find attached all the bugs I have reported in my current project” /Jesus, you make us feel guilty although we didn’t ask you to commit this sin/
  • “Please find screenshot of my automation test report for the current project I am working on” /Doh!/
  • “Sorry, can’t send” /What?/
  • We get a mail, “Yes, I do test reports in office” /Did you really read our careers page?/
  • Another mail, “Test Reports: I am confused” /Well, thank you for the test report/
  • Some two intelligent testers googled for test report and sent us the sample test report template as test reports and are asking us did we get it and when they’d be called for interview
  • Another mail: Can you please help me in telling what you want in test report? /Well, good question. We want you to test and send us the report of your testing/
  • Another mail: “Test Report: Yes”
  • All test cases pass, nothing to report /Wow, whata tester :P /
Some tips:
  • The way you apply to a job could matter to get you to an interview. The way you conduct yourself in an interview could matter to get you an offer.
  • If you need to prepare technically for an interview, you could be under skilled.
  • If you don’t know about the company to which you are applying, you don’t deserve the job.
  • If you haven’t tested (and bug fixed) your resume, you shouldn’t bother applying to testing work.
  • If you want a specific salary which is thrice or twice as much as you are currently earning, you need to be a rock star.
  • If you have a different career plan than the job you are applying to, you won’t be happy with the job and the career.
  • Get a professional resume written. Don’t be stingy, pay money to get it done.
  • Don’t lie in interviews. At least in the testing circles, we are well networked to find out things, if we need to.
  • Be professional /You know what that really means?/
  • Don’t fake. For God’s sake.
  • Don’t put your current employer down, they are at least helping you have a living.
  • Never, ever, never, ever make a jump to another company just for money.
  • If your covering letter is poor, we don’t go to open you resume/CV.
  • Moolya asks for test reports, not from your current or past work. We want you to test an open source project and send us that report.
  • We are tired of Akel Pad, Gmail and Google test reports unless you have something interesting or different.
  • If you mention a technology in your resume / CV , ensure you really know it. Otherwise you are losing out your own chances.
  • Your first impression (and successive ones) matter a lot for us to consider you for an interview.
  • If you pretend to have passion for testing, it is easy to find out you are not.
  • What organizations really look for is “Can you learn?” and again it is easy to find out if you don’t belong to the category.
  • In case Moolya rejects your application, it doesn’t mean you aren’t good, it means, you don’t fit our current bill.
  • Organizations like to maintain a culture at work. If you turn out to be a Nana Patekar of Angi Sakshi , you won’t fit most good cultures.
  • Please understand that every company is different. The way it works in Moolya could be lot different.
  • The kind of colleagues you work with matter much more than the salary of your colleagues.
  • If an organization is hiring a lot of bad testers, please don’t join them, even if they offer you more salary.
  • Don’t put all email ids in TO when sending your profile / resume / cv. Put it in BCC. We hate to be spammed by others.
  • If you practice testing (like how Dravid does with Cricket even off the matches), we would be happy to hire you.
  • Ask yourselves if you are another head to be counted or you are a brain that’s needed for the organization.
  • To be hired by Moolya and become a Moolyavan there should be some moolya you already have and some moolya you could bring to in future because of your moolyable ability :)
Best wishes from Moolya.

Three stories of 2011

Happy New Year! Below is a letter / mail I sent to everybody at Moolya on 30th December 2011. I am publishing the same after modifying to suit publishing in public.

 

Dear Respected Colleagues,

Greetings!

Today is the last working day of 2011. I feel happy and sad. Happy that we have done a great deal of things together this year and sad that this wonderful year is ending. I hope the coming year is as good as 2011 or even more good, for all of us. A very large percentage of how 2012 is going to be depends on us.

Here is a story from 2011 that actually took place in 2010.

I must have spoken to about 10,000+ testers (or maybe more) so far through conferences, workshops and other community events and a couple more thousands through my writing. I have been blessed to be bombarded with a lot of questions and personally I have been great in answering it. So, I had assumed that I can answer any question about testing or learn from it, if I don’t know. When I wanted to start this business, most people I talked to about it were asking about a business plan that I should have had. What they meant by it is; how will Moolya make money? I couldn’t answer that question. “I don’t have an answer for that in the way you want it but Moolya will make money through good testing” is all I had to say. Later I started to think deep about the business plan and somehow I didn’t know how to get a business plan for Moolya. I lost sleep trying to answer this question. I kept asking myself, “what’s the business plan, Pradeep?”

I don’t have an MBA to have learnt the theory behind a business plan. I looked into several business plans available on the internet and started to look at elevator pitch of several budding entrepreneurs. Despite all that, I didn’t find even a clue for a business plan for Moolya. This bothered me a lot more and I lost the little possible sleep I used to get. I started to look at all testing services companies websites trying to understand what they are telling about their business. I shouldn’t have been surprised. All of them were talking the same thing : “we will save cost for you, dear customer” and as I know how they do(nt do) it, I was sure Moolya was not about saving costs for customers perhaps it could increase it for all good reasons. What was echoing within me is “That’s not business plan, Pradeep. That’s just a marketing statement. It would take a lot of time for people to believe what you say”. So what is Moolya’s business plan? I have been a consultant to several companies in the past. I know the business plan for such services companies is offer 0.5x dollars of billing per hour instead of x but have 4 people instead of 1 thereby making twice more money than what the context demands. “That’s not business plan, Pradeep. That’s what companies who lack integrity do”.

After enough of looking outside, I decided to find the answer within. I was asking how did I make money as a consultant? I did make money doing some good testing (ahem) and good marketing of good testing and good care for the community and good care for my colleagues who also wanted to do good testing. “That’s the business plan, Pradeep”. I woke up one day and said, “Moolya will make money through good testing”. Turns out that the answer I got after all the research was the same as the answer that I gave even before I started the research. I find that fascinating. I started to do a research on how my answer prior to and post analysis was the same. My education suggests me that I didn’t recognize that a business plan can be as simple as that. Had I not educated myself well, I wouldn’t have been able to recognize all this and there wouldn’t have been Moolya, there wouldn’t have been you in Moolya and also there wouldn’t have been this email.

Here is a story of 2011 that actually is going to take place in 2012

So, we have cracked the puzzle. Good testing brings in good business. Today, we have some requests from international organizations that if we were to process it in 2012, we may double or even triple our number of people, operation size, revenues and profits. Our good testing of the past has been helping us bring good business but what will help us in retaining it is – you and your testing. If you do good, we will retain, if you do great we will grow. If you do bad, we shall crib about recession together. I have no doubts about it.

In 2011, I have made some great, good and bad decisions. What matters to me is how big a proportion is “bad” as compared to “great” and “good”. Also what is the magnitude of “bad” even if I committed it once. My goal next year is to not bring down “bad” decisions by number but reduce the magnitude of it and also increase the magnitude of “great” and “good”. Moolya has constantly demanded me to change and adapt to changing situations and context without losing integrity. Just because I was able to bring great business, people and money into Moolya doesn’t mean I have done a great job. I think I could have done lots better and we could have been in a better shape. I hope and promise to you that in 2012, I would be more efficient and more effective.

In the journey, I am asking myself everyday  “What is Moolya’s business plan? Has to be “Good testing + ‘something’ “. A question of “What is that something, Pradeep?” has kept me awake over the last couple of weeks. I don’t have an answer for it yet. Maybe I am destined to find it only in 2012 but my quest to find it out is on.

Here is a story of 2011 that actually happened in 2011 (for a change ;-) )

I have relied on the core team for everything I wanted to share. Be it good or be it bad. Without these people I wouldn’t have been able to get the slightest possible good sleep I got this year. I am fortunate to have a great core team. There are more good people joining in future to be a part of this and I am just waiting for people like XXXXXX, XXXXX and XXXXXX and a dozen other cool testers I know to be a part of this great team. This is possibly one of the best line up of testers within a single company in India. Such a big dream come true to get all these people together and to get them working with each other. This is the team that can actually take our company to a level I can get it to grow to levels beyond that.

I need the core teams’ support to help me help Moolya and they need your support to help them help Moolya :) So, are you support executives here? I care about creating a 2nd wave of leadership team at Moolya who can create a 3rd wave of leadership team, which is, you. 3rd wave doesn’t mean you are below the 1st and 2nd, instead it could also mean you are ahead. I am hoping that the team I closely work with will not do mistakes I have done in past and they would take care of you to not do mistakes they and I have done in past. I am hoping you would do new mistakes to be able to help the nth wave leadership.

You might know that this core team spends a lot of time for you. Why? That’s exactly the point. If all we cared is how much money we make per person, we won’t bother to care if you have been learning well or not. The 3rd wave of leadership team, in my personal opinion, going to decide the long time future of Moolya. If young people like you don’t become leaders (real leaders, not by designation such as test lead) then it wouldn’t make me happy to enjoy the money I may make in future.

That brings to a point I found out about Moolya. Moolya’s business plan is about good testing + care to people, communities and our craft + something. “What is that something, Pradeep?”

I want to wish a Happy New Year to you and your family members. I wish, you re-invent yourself, this 2012 and show the world who you could potentially become in 2013. Many thanks for the great support you have offered to me and our company, Moolya. I love you all.

Cheers!

Pradeep Soundararajan

Sponsoring a child’s education for an year for every new customer we add

This is not a publicity stunt. We should have kept it with ourselves but we also see a reason why we should publicly announce it.

Moolya is going to sponsor a child’s education for an year for every new customer we add. Education means a lot to us. We are who we are and we will be who we will be because of our education. My parents could afford education although they had to make a few sacrifices. I am sure every other middle class parent made it. If there is nothing to sacrifice to educate a child, they are really poor. We want to help such people educate their child.

Today, 2nd November, 2011, we added our 6th customer, our 2nd multi billion dollar customer for whom we are going to be testing a portal that caters to millions of users every month. We hope to do some real good work for them and help them maintain their status us a leader and help them make progress in what they want to.

It is an emotional moment in our office that we are getting good work and in turn doing some good to the society. We shall keep you updated about what’s brewing with us. Hey, we haven’t completed one year yet. So, for a start we have done reasonably well and this could not have happened without the blessings of our parents, our gurus and our fellow testers worldwide.

Lets talk more about the child’s education thing. We sponsored a 4th grade student Deepa from Bangalore whose mother is a house hold servant. Deepa’s father left his family and absconded a couple of years ago. Deepa is now studying 4th grade supported by Vidyanikethan and we sponsored her. There are about 48 more children who do not have sponsorship from Vidyanikethan, so if you could help them it would be great. There must be about 4800000 more in India and 4800000000000 more in the world. No matter where you are, please give back to the world that chose you to be lucky as a kid and other kids to not be as lucky as you are.

We wish to grow big, huge, magnificent or whatever word that suit to this context to help more children be educated. Just because we are in India, it wouldn’t mean that we will choose to sponsor children education in India. We hope for our subsequent customers, we will choose countries in Africa or any other place or location you could help us know where the need is .

We saw TED videos of an African teenager William Kamkwamba who created a windmill, made it work and generated electricity and  Patrick Awuah found a university in Ghana after working for a while with Microsoft in USA and talk about how educated needs to act. Those were inspiring ones and we need more such people for the world. Be it from India, USA or Africa.

We hope to make the journey of Moolya useful to more people than just our customers, our employees and the vendors to whom we give business. We thank all our customers, employees, mentors, gurus, parents, friends and well-wishers for enabling us to do what we are doing.

The lesson we learn is, we don’t need to be Bill Gates or Azim Premji to do this. All we need is enough education to care about others education.

Thank you!

Twitter driven exploratory software testing

I don’t think I was the only one who invented this but I have become personally good at building this as a skill and an approach to test software and I am also starting to teach people how to do it. I mean the idea of using twitter and other social networking platforms to understand what users really want versus what is being delivered to them, what requirements should changed to, who our real customers are and more.

One of Moolya’s customer, hundreds of million USD in revenues, hired us to consult them in doing brainual testing. So, we as a services company didn’t say, “OMG! Why do we need to tell you our secrets?” but instead we said, “That’s cool. We can help you do that”. There is no secret ingredient in our secret ingredient soup.

I am not supposed to tell who the customer is and who their customers are nor the projects they work on. So, those things remain a secret. We consulted for about 12 different customers they work for.

One project was a portal targeted to be used by North Americans and if I tell you the website, you’d agree that the website receives at least millions of hits per month. Americans use it to buy something. No, it is not Amazon, eBay or something like that. Lets assume they buy something with it.

The users of that portal have plenty of alternatives. So, if the website doesn’t help the users do what they want it to, users are likely to go to another website and still buy that because they need something :) When a lot of users move away from a specific website, the company is losing a lot of revenues. This could result in heavy losses.

I went through tons of test case documentation that were being executed for every build and was trying to determine if the test coverage is as good as the claim made to me was. I logged on to twitter and searched for the customer twitter handle and searched for their company related tweets on twitter.

I was shocked that there were lot of people complaining about not being able to buy what they want to. Was the company paying attention to it? Sure, they had a large support team to listen to those who were kind enough to call them. Hey, most of them have started tweeting than calling up customer service.

As an example: Let me take some website used by Indians irctc.co.in which is known for its poor quality yet people have no alternative so we are forced to use it. Imagine, if they had an alternative, a good one, then irctc.co.in would lose all the money they are making.

So, let me get on to twitter and find out what users are telling about it:

At this moment, if you think you can gain the skill I am talking about just because you too know to search on twitter, you might be mistaken. Read on.

Look at the following tweets

“@IRCTC Shame on you guys. You should change your site name to ‘serviceunavailable.co.in’ or ‘wefoolscantscale.co.in A friend’s status in FB” Source:  http://twitter.com/#!/itsBritto/status/127773267250524160

“IRCTC … u r a disaster …. atleast u ve become one !Source: http://twitter.com/#!/munna_geek/status/125144094421954560

“There is this permanent scroll on irctc site-”Due to technical issues the website may be sometimes slow.The inconvenience is regretted.” Gr8″ Source: http://twitter.com/#!/Vjuneesh/status/127618207484874753

“In 2 months IRCTC has wasted my 24 hrs.. F’in hate IRCTC…” Source: http://twitter.com/#!/FrogOutOfaWell/status/126194331987099649

The above tweets determine the emotions of people using the software. Emotion is an important oracle in software testing to determine if there is a problem with the software. I would use the above tweets to help the stakeholders what emotions people are undergoing while using the software. It is an important information I am going to provide to the management and ask them,”Is this is how you want to treat your end users?”

Look at the tweet below:

“So IRCTC breaks my heart yet again. One extra evening in kgp vs. additional 4.5k on flight tickets. Decisions… decisions…” Source: http://twitter.com/#!/shubhadeeproy/status/127751378503335936

I’d use the above tweet as a meta data to what I want to go find out more about. So, my meta data becomes IRCTC & Flight to determine how many people want to use the train but are forced to taking a flight. I would investigate and present my findings on how many such cases are reported in a period of a week and how many cases might not even be reported and the potential loss estimate.

The other idea on twitter is about knowing the hashtag FAIL or #Fail , so I associate what I want to search with #fail and see if there are people reporting tweets with those hashtags as well.

So, I found this one interesting:

“Dear irctc,don’t you understand meaning of seat preference?I ask for a window seat and you don’t give when you have around 100 vacant? #fail” Source: http://twitter.com/#!/pallaviagashe/status/126295561463791616

The above tweet helps me direct my testing to determine if there are problems with the algorithm that allocates seats based on users preferences.

As an interesting extension to that, I would direct my tests to determine if user was informed that there are no seats of their choice available but they were informed about it in a real estate of the website that most users are not paying attention to.

The other set of ideas are about tweets like the one below:

“Tired of IRCTC. Can we have private railways? Atleast we’ll have better customer care :-/” Source: http://twitter.com/#!/SocialPaparazzi/status/127241752313741313

This is someone who appears to have written to customer service or the so called “care” division.  I may want to search more patterns of what people have thought about its customer service. That helps me find tweets like the ones below indicating how the customer service might be appearing to work in this organization.

“IRCTC website takes customer for a ride to claim refunds: Booking tickets on the Indian Railways ” Source: http://twitter.com/#!/GlobalNews247/status/127268255785160704

and “Dilli IRCTC cust care guy takes my call n spells Madaan as M for Monkey; A for Awaara; D for Dog and N for New Delhi… #AnnoyinglyHillariousSource: http://twitter.com/#!/nainymadaan/status/125158568637898752

So far, I have exposed many different aspects of the website and what users want and don’t want and have shown how what these users say impacts my testing. So, there is more to it than you see.

Just check how much of power this offers to you as a tester on bug advocacy and how much power it offers to you as a tester to sell the bugs you find to developers. I did try it out. I said, “Hey look, this is not what I say, this is for whom you are actually writing the code is saying. You don’t care for what they say?”

One other thing I do, is to check for various quality criteria problems being reported. Hey, users are not testers so they don’t use our language. No one would tell you, “I am facing a reliability problem here” but instead they’d tell something like this:

“Yes irctc, your homepage is very pretty and informative, now let me login!!!! :@” Source: http://twitter.com/#!/MehMitali/status/126505387074650112

No one would tell you, “I think the session time out value should be increased to 60 more seconds but they’d tell something like this:

“My session has expired :S WHAT IS WRONG WITH IRCTC! Aaaaarhg!” Source: http://twitter.com/#!/PuviTweet/status/126926320369270785

“IRCTC site is pretty irritating, session expires after a couple of clicks” Source: http://twitter.com/#!/ankit_seth/status/126997658836533248

So, deciphering the quality criteria you want to search for and mapping it to what the user language could be is an interesting exercise.

I spend time figuring out any detailed explanations or conversations between people about the service or product. One such is shown below:

“Looks like Cleartrip.com fetches the data from irctc.co.in ! interesting. So if irctc.co.in is down.. so is cleartrip :) .. Yup. The only difference is the interface. I use it for searching for trains and then book it using irctc.  ”  Source: http://twitter.com/#!/kshitiz/status/126348777505304576 / http://twitter.com/#!/kshitiz/status/126348871151534081 / http://twitter.com/#!/kshitiz/status/126349344654893056
You may wonder why this is important. These people might be willing to spend time if I want to talk to them. In Feb 2010, I was hired to test a portal here in India that literally had half of the internet using population of India using it. There’s one thing we did is to figure out which of its users were willing to spend time providing feedback. We tracked those people based on their conversations and time spent on those conversations about the service on twitter. You must know they were pretty excited that the organization called them up and wanted to listen to more of what they had to tell.
Now, some testers and techie folks are also on twitter using such software and they may end up writing bug reports that are a good read. For instance, take a look at this one:
“Gotta firebug #irctc and write a script, seriously. Stupid captcha din’t load in last bookingSource: http://twitter.com/#!/coditoin/status/126491389365202945
I have just spilled a few beans from the can of worms you can uncover by using twitter driven exploratory approach to software testing. You could help in spreading this message to more testers. Most importantly, you could share your practice of this approach in the comments section or contribute new ideas to us.
I tried spreading this to some Indian testers in some Indian IT services companies. They only had one problem, “Our company blocks all social networking websites and hence we can’t do this testing” to which I replied, “Fellas, I see smart phones with GPRS / 3G enabled in your pockets, I am sure your organizations cant block internet access to that. Sashaboyee!”.
At Moolya, this idea is a part of our testing culture. Tomorrow, if you are getting a proposal from any services company that tells “we do twitter driven exploratory testing”, maybe you’d tell who taught them how to do it. Skadoosh!