I wandered thinking how to test the Cloud

Does the title line sound like something that you have heard before? Yes, remember the English lessons you took during high school days. Yes, i have slightly modified the line "I wandered lonely as a cloud" from the poem "Daffodils" by William Wordsworth. So, what is this article about? Is it about introducing readers to English poets? No. This article is about "Cloud Computing", around which there is a huge buzz in the software industry today. Analysts predict cloud computing to form the next big wave in technology infrastructure and are also talking about lot of other terms such as SaaS(Software as a Service), PaaS(Platform as a Service) etc in conjunction with Cloud Computing.

Now, let me refrain from discussing about Cloud computing in detail since i am oblivious of the nitty gritties. However, i have limited exposure to SaaS, which i understand as a model in which software will be centrally located somewhere in the internet(cloud) as opposed to storing them in local machines.The basic idea is cut down the expenditure on hardware/software.

To give a simple example, lets say there are 3 star hotels in Chennai and all have their own software/hardware to manage their services. Now, Software as a Service is a model where a vendor comes and offers to manage the hardware/software for all these 3 hotels from his premises and thereby enables the hotels to use the software on a demand basis through virtualization and relieves from all the issues related to managing their own infrastructure. Certainly makes life easy, isn't it?

Now what are the challenges in the cloud world particularly when it comes to testing?

Configuration and Customization
Each of the hotel's software can have a different workflow and hence the vendor needs to make sure that when the user for "Hotel X" logs in, he is able to view only the screens pertaining to him. Customization should also be looked at from an Integration testing viewpoint

Security
The SaaS provider needs to ensure that the data of all his clients are maintained properly. He cannot afford to mess with the data.

Monetization
Since software will be used on a demand basis, the charges will be made as per the usage(something like electricity). So, testing also needs to take care of this aspect.

Performance Testing
Clear cut goals with respect to Response Time, Throughput, Maximum load supported should be identified and the same needs to be tested carefully.

Paper Submission for ASTA

I am planning to submit a paper in this year's ASTA (Asian Software
Testing Alliance) International Software Conference 2010
which will be held in Vietnam's Hanoi and Ho Chi Minh cities between the 2nd and 5th of November 2010.

There are 3 categories under which papers can be submitted. People, Process and Technology are the 3 categories under which different headers are available to select for paper submission. Under the "People" category, "Testing Skills" is the title on which i intend to submit my paper. As a prelude to the paper submission, the conference expects the participant to send an abstract summarizing the paper content to them.

Under "Testing Skills" i am planning to write about some interesting areas which i have learnt over the years. I will continue to post more information on the abstract, how my paper is shaping up and the obviously about the areas that i plan to cover in the paper under the title "Testing Skills".

Rendezvous with TesterTested

My company's "Talent Nurturing" team were discussing with me about their plans to hire an external consultant and conduct a 1 or 2 day training session for our Testing DU (Delivery Unit) and during the conversation asked me to suggest some good topics that will benefit the attendees. As someone with the experience of being coerced to attend testing training sessions by my employers in the past, i was not keen to recommend a standard training program where you have the trainer talking about concepts that will never help the tester improve his skills. Some examples are, what’s the difference between Sanity and Smoke testing, contents of test plan, what exit/entry criteria exactly mean, bug life cycle, how to have better communication with the developer, how to know if automation is good for your project and finally asking the attendees to write testcases for Yahoo mail as a exercise. Apart from the trainer (he receives a fat pay cheque for the consulting from the company) no one else really derives benefit from such sessions.

So, i suggested that it would be good if we can introduce our testers to the "Context Driven School of Testing" which specializes in approaches such as Exploratory Testing, Rapid Testing etc. The very fact that the context driven school emphasizes on areas like Lateral Thinking made me recommend it as i thought our testers stand a chance improve their skills to "test" better than what we were currently doing. With the idea being accepted, i was not able to think of anyone else apart from Pradeep Soundararajan, who is leading the context driven testing efforts in India.

I sent a mail to Pradeep explaining the need and he in turn consented. Pradeep also compromised a lot on his pricing since he was keen to share his knowledge and experience with the group to help them become better testers. As expected the session focused on puzzles for testers, lateral thinking etc and also questioned our primary understanding of various testing concepts. For example, we were not able to explain the exact meaning of testing despite the fact that we use the term at least 100 times every day. Pradeep also gave us some exercises to help us improve our testing approach and taught us about better defect reporting methods. He also emphasized on the need to use tools when it comes to testing. No, not automation tools but tools like AllPairs, Perlclip etc which can help the tester expand the coverage of testing and subsequently raise the quality bar.

Overall the session helped us to introspect the way we were doing testing and opened our eyes to newer aspects of testing.

ASTA Testing Conference 2010 Vietnam

Please visit http://www.vietnamesetestingboard.org/zbxe/?mid=notice&document_srl=291844&listStyle=&cpage= for more details

Vietnamese Testing Board(VTB) is considered to be the #1 Software Testing Community in Asia with more than 1,00,000 members.

Getting outlook email metadata.

I want to get access to an msg file (standalone, outlook message file) and read all of its metadata (like To,cc,bcc, size,from,sent time etc..)

Which language will be useful in achieving this in an easy manner?

In addition, will outlook API can be used? If it is , then any code samples please?

Any help,would be appreciated.

A Myth called Test Automation

In the past 6 months, i have seen a lot of prospects asking only for Test Automation from us. Though we clearly say that without manual testing it doesn't make sense for them to move towards automation, they really don't seem to care. As a services company, we also do not stress on the importance of manual testing again and again for the simple fact that we can lose the prospect from being converted into a customer. But personally, i feel bad that we are showing them the wrong direction and also knowing that the automated scripts won't be reused after a period of time, i feel sorry for them since i am aware that they are not going to reap return on their investment. Test Automation is considered to be the "Silver Bullet" by many companies today for all their testing problems.

Product Companies in India...

I am working at a software product company. Many of my friends are working in product companies. Though I am in Product Company, originally I am from Service Company.


I am seeing a model difference (as everybody knows) between service and product companies in India. Here in product companies, there is a collaborative development model, or in other words collaborative business model. The American company is not treating as client but as a parent, the American workers are treated as peers.


Definitely there may be many thought patterns would have ridden over it, but my opinion is, this is not good for both Indian as well as American wings. Indian wing should its American counterpart as its client, which not only increase the internal competency but also greatly justifies its existence.


As a company, either we have to bravely innovate things or should satisfy our clients/customers... Most of the core customer relationship activities are done in US, Indian companies start enjoying the 'non-pressure' of customer satisfaction... Even if it is created, it lags direction...


Then when Indians can treat their American counterpart as peers? In simple words, over the years, i.e. if process, knowledge, maturity of Indian wing is optimum, obviously the 'Equality' will emerge. Attrition plays an important role here.... Say if an ODC in Bangalore/Chennai is having contract with an American company for the past 6 years and with minimum attrition, then it’s the time for treating 'them' as your 'peers'