360Logica.com

The Client

Our customer for OS compatibilities is http://www.dualalign.com, they developed a products for High Impact Image Applications and all 3 softwares are Desktop applications.

For browser compatibility test requirements, Our customer is leader in Online market Place - www.elance.com .

The Requirements

• DualAlign required to ship their products on different OS Windows, Mac and Linux. 360logica supposed to perform compatibility testing across all different OS and produce compatibility issues.
• Elance is leader in onlinemarket place and asked us to perform regular testing on all available browsers and OS.

The Solution

• Identification of Matrix of all OS and resource scheduling.
• Defined tasks and QA deployed for dedicated OS testing for Dual align products, produce separate reports for each OS results.
• Browser testing for Elance, we identified all popular browser and their old and newer versions. We prepared matrix of those information's and used QA resources for one version of one browser. VM ware helped us to perform testing on different browser on different machines.

The Technology

• OS for Dual align tests : Windows 2000, 2003, NT, VISTA, XP, windows 7, and MAC
• Browsers: Internet explorer versions 6,7,8, Firefox versions 1.5, 2.0 and higher, Opera, Safari on windows and Mac both
• VM ware for virtual machines creation
• MAC OSX

Contribution

• Challenge was to set up different OS and browser environment
• Resource allocation for every combination of OS and browser
• This involved the development of various OS and browser combinations and generating the environments.
• Performing the functional and browser compatibility testing across these combinations of operating systems and browsers.
• Worked closely with customer to understand product
• Establish a bug reporting mechanism for efficient and quick bug fixing.

You can also download the case study here.

Software-as-a-Service - from vendors like NetSuite and salesforce.com - has democratized the software industry from RFP to purchase to rollout. Unlike complex on-premise deployments that carry a hefty price tag and require weeks for vendor selection and months for rollout, SaaS provides a quicker, lower-risk alternative to traditional licensed software that empowers the business unit by:

• Enabling business units to own the buying cycle.
  Business users now have a software option that allows them to control the buying cycle, in contrast to pre-SaaS application purchases that required IT involvement - to short-list, demo, and approve solutions as well as corporate involvement for budget sign-off. With SaaS, line-of-business heads ranging from the vice president of sales to the vice president of HR can single-handedly own the decision by taking advantage of free trial offers on Web sites to evaluate solutions and paying a monthly or quarterly rate low enough to stay off the corporate radar screen.
• Eliminating dependence on IT.
  SaaS allows business units to roll out and manage day-to-day application needs, providing an alternative for users who don’t have necessary IT resources available or IT’s cooperation. One customer we spoke with said, “Our division looked at SaaS since we couldn’t use our headquarters’ IT department. They weren’t willing to support us at all.” Since part of the SaaS appeal is freedom from IT, vendors have focused on creating easy-to-use, point-and-click tools so that business users can set up and configure solutions with little technical knowledge and minimal specialized training. For many users, SaaS wizards for creating custom reports, changing roles and access rights, and building custom layouts means an end to waiting on an IT project list for days or weeks until resources become available.
• Facilitating ongoing development and innovation networks.
  Because firms running on a multitenant architecture are all running the same code base, user firms, channel partners, and SIs can choose to reapply one deployment’s customizations to another through templates, creating economies of scale not possible with on-premise implementations with modified code. Moreover, this co-development speeds innovation and enhancement by letting developers build off each other’s work. Vendors like salesforce.com and Salesnet support publicly accessible developer sites that provide free sample code, best practices, and forums for developer discussion. Salesforce.com’s developer community has gone one step further by growing an open source developer forum on SourceForge.net.

Cucumber is a functional test automation tool for lean and agile teams. It supports behaviour-driven development, specification by example and agile Acceptance testing. You can use it to automate functional validation in a Form that is easily readable and understandable to business users, developers and testers. This helps teams create executable specifications that are also a goal for development, acceptance criteria and functional regression checks for future changes.

Why Use Cucumber?

Cucumber is one of the rare tools that try very hard to stay out of your way, to let you do your work without making you worry about the tool itself too much. It helps teams automate their specifications efficiently in several ways:

• It is relatively easy to set up.
• It supports multiple report formats, including HTML and PDF.
• It supports writing specifications in about 30 spoken languages, making it easy for teams outside of English-speaking territories or those working on internationally targeted software to engage their business users better.
• It supports different ways of describing executable specifications —including story-like prose, lists and tabular data.
• It allows scripting, abstraction and component reuse on several levels, allowing both technical and non-technical users to efficiently describe specifications.
• It generates the tricky parts of the code so that you don't have to write most of the boiler-plate automation or make mistakes doing it.
• It integrates nicely with the rest of the development ecosystem. It does not try to impose a version control system, but works off plain-text files that can be stored in any version control system. For continuous build integration, it emulates JUnit (and everything else in the world is already integrated with JUnit).
• Although it is a Ruby tool, people who work on other platforms do not have to learn Ruby to use it. You can use Cucumber with .NET or JVM languages almost natively.
• It's integrated with all the most popular web testing libraries.
• It allows you to mark tests with tags so that you can quickly run a group of related tests (eg quick tests, slow tests, integration tests, accounting tests).

This video provides a brief introduction and overview to the basics of software testing.

This testing services introduction covers both manual and automated testing as well as software product testing, unit testing, integration testing, system testing and acceptance testing.