Multi-device eLearning Testing

A well equipped lab of physical devices for reliable multi-device testing.

In today's multi-device world, eLearning needs to be supported on multiple combinations of browsers, manufacturers, models and sizes, operating systems, connectivity modes and platforms, etc. Apart from designing multi-device eLearning, it is also necessary to ensure that eLearning works properly on multiple devices. This can only be achieved by thorough testing, that too on various actual physical devices and configurations; a kind of infrastructure that is an absolute must if testing in multi-device world has to succeed.

Our Testing Lab for Multi-device eLearning is the answer to this challenge.

And, how do we do it?

  • Infrastructure
  • Experience & Expertise
  • Advantage
  • Process

Our Testing Lab for Multi-device eLearning is well equipped with a variety of devices running different operating systems and browsers. Devices with screen sizes between 240 x 320 and 1280 x 800 pixels, as well as some high-DPI variants, Windows PCs, Macs and laptops for testing larger displays; tablets and smartphones, running iOS, Android and Windows for the smaller screens; along with tools such as Adobe Edge Inspect and Ghostlab to help in quick and holistic testing.

Fool-proof solutions

Our decade long experience, extensive domain expertise and know-how of the latest tools and technologies translate into error-free projects that deliver on their objectives.

Zero delays in delivery

Our dedicated team of testing specialists, well-established testing infrastructure, and time-tested testing process reduce the project turn-around time considerably.

Cost savings

You don't have to purchase specific devices, nor do you have to hire special skills or invest your time in testing.

Our testing process runs through five broad stages.

  1. 1

    Requirement Analysis and Proposal

    We establish a basic understanding about the technology to be used to develop the course, the nature of the content and treatment, the structure and duration, the target devices and configurations, the delivery method and the testing specifications. Based on these, the required time and resources are estimated, after which we submit a proposal.

  2. 2

    Project Initiation

    After the Business Proposal and the Project Scope Document are finalised, the project is initiated. We now address project planning, and set up internal systems for communication and project management, and version control.

  3. 3

    Test Strategy

    We detail the activities to be carried out, in sequence. This includes defining the testing environment, the scope of testing, the documents, references & standards, and the internal & external mechanisms for issue tracking and reporting.

  4. 4

    Test Cycle Execution

    Our team carries out testing on the actual target devices, using various combinations. We create test cases, test the content and/or GUI and/or navigation and/or standards and compliances and/or global functionality, record issues and create test reports.

  5. 5

    Delivery and Closure

    After the testing on actual devices is done, we send out a final delivery confirmation mail along with the final Test Report, Bug Density Report and a bug-free package.

Resources