Software as a Service (SaaS) has changed the way software’s are delivered to end users. Web2.0 has changed the way content is created, controlled on web. Product Development 2.0 is changing the way software products are created. Enterprise 2.0 is changing the way organizations works. With wind of change sweeping the user and developer community, how can Testing, Quality be spared…? Be ready, we are Introducing Offshore Testing 2.0.

Testing 1.0

In Traditional mode of testing organizations would typically create a test script/ test plan based on requirement documents provided by Client. Post test plan creation and Application development prior to UAT, testing team would perform various testing including

• Unit Test.
  • The entire source code is divided into modules, module in turn are divided into smaller sub module and units
• System /Integration Test
  • Once the modules are integrated the testing done at this stage is called system test. This test usually checks for data flow, checks conformance to data appearing in requisite format etc
• Functional Test
  • Testing if workflow /logic associated with system is achieved
• Performance Test
  • Stress testing and load testing to check the capacity of application under actual usage. In most cases is done via automated test scripts
• Beta Test
  • product Given to select user group to find out more testing defects
• Automated testing
  • Tool based approach to automate testing stages

The entire testing would be done by a single organization, using its resources. There are definitely some issues in Terms of organization not meeting testing schedule, Time taken in Ramping up resources, Learning curve, so on and so forth. Introducing Offshore Testing 2.0

There is no denying the fact that Offshore testing generates lot of value for outsourcing organizations in terms of augmenting its capacity to access resources/technology and cut down time and cost. The benefits would still have been greater, if the principles of web2.0 viz. collaboration and power of network was applied further.

Even though QA/QM/Testing methodologies have existed for long times, yet organizations have failed to value its networking value. More often organization accept less testing to testing through network (of product user, user community).

Testing 2.0

Explaining Concepts in testing2.0

Testing2.0 is

1. Collaboration+Testing
2. Contribution+ Testing
3. Social networking + Testing
4. Wheel+ Testing

Collaboration+Testing

• Team of software professionals testing an application/ Product working in an organization or on network, is Apha testing
• Network of potential/ present customer testing application is BETA testing
• Random set of users invited to test application (Distributed modules) is random user testing. If you can split an application in portions, functionalities etc. This is similar to Collaborative cracking of password, codes, games played on LAN, games tested on LAN

Contribution+ Testing

• Result in testing 2.0 should not matter if testers are connected or Independent. What should be more important is :- Test should be carried out independently
• Testing 2.0 contributors should know that they are testing for cause and network of tester should be built based on synergies.
• Network of People would best know different test technique and when to implement what. Also synergy obtained from network of people expert in different form of testing.
• Wouldn’t it be great to have/ build of a community of tester, where test and specification can be routed to tester best suited for kind of testing ( Black box, White box, Automated and so on). A System to route tests automatically to best tester.

Social Networking+ Testing

Let’s look at few scenarios, before illustrating use of Testing2.0 through a story

• People know people.
• People exchange emails about tests. Barely old.
• People exchange SMS. Instant notification. Want it.
• People notify the right guys.

So many times Would the tester hear “You didn’t find nothing, That bug was discovered by Sidd, 1 month ago.” Sidd workarounds it and fixes the bug. Leter Sidd resigns. And now what? How many times you would say “Hell, why that bug didn’t reach me before, so i didn’t waste time finding it, understanding it, and the bug will be fixed prior to customer review?”
Bugs know people. Hello. I’m a bug found in X, being tested by Y and Fixed by Z. Social connections says Z can fix me. Let bug crawl the network to reach Z who can fix me. That’s future the of testing and Bug Fixing.. That’s the power of Testing 2.0. Power of harnessing feature of Web2.0.

Wheel+ Testing (Steps to Inclulcating Testing 2.0 Cultures)

The idea is not to re-invent the wheel, every time we test. The basic idea is to promote and share learning. While testing an application either in an organization or on network of tester, recording the steps till bugs were found and fixed can decrease the time to fully test the application or alternatively test application more.

• Record all steps until the bug come out.
• Prepare a report filled with all data
• Use Human Comprehensive data
• Use metadata = Tags
• Link to resources, to the Testing 2.0 network, to the other guys so they can test and share
• Build a reveue model, that encourages participation of testers of networks
• Route test result/ Bug reports to the best guys for bug fixing
• Store needed data in distributed places = network storages
• Take screenshot and put it on Flickr. Enjoy other testers put notes over the screenshot like a board.
• Take videos when necessary to illustrate testing process. Use YouTube.
• Score a bug in collaborative way = like Digg
• Use modern communication and collaboration tool, to share information.

Testing 2.0 in Use

• Already open source community, uses principle of testing product by network of users/testers in every release of product
• A public bus/ Issue list, when getting product tested would definitely help adoption of testing 2.0
• A growing community of users on various networks who test and report bug on different software and hardware platform.

Conclusion

Collaboration, power of network, collective intelligence is driving the world of technology and business. At a time when every aspect of business is changing to use collaboration and power of network, testing 2.0 will definitely making testing a more complete process with lesser errors and in lesser time.