Browse Prior Art Database

Method and System for Shaping Product Usage during Pre-Release Testing Stages

IP.com Disclosure Number: IPCOM000233986D
Publication Date: 2014-Jan-06
Document File: 2 page(s) / 71K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system is disclosed for shaping product usage during pre-release testing stages. The method and system provides access to all functionalities of a product to users who are participating in a beta testing program of the product.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Method and System for Shaping Product Usage during Pre-Release Testing Stages

Typically, it is common for a nearly-completed product to be made available to a

wider range of users under a beta test. The problem is that while beta testers may use core functionality and common methods of the nearly-completed product, lesser-used functionality or features that were made for specific situations are least frequently tested by the beta testers. The challenge is to allow users in a beta program to gain early access to the nearly-completed product while ensuring that all functions are tested, not just the features that most beta test customers want to use.

Disclosed is a method and system for shaping product usage during pre-release testing stages. The method and system provides access to all functionalities of a product to users who are participating in a beta testing program of the product.

In accordance with the method and system, developers of a product may conditionally block certain functions or methods to guide beta testers towards areas that need to be tested. This is performed by allowing beta testers to use core functionality or a common functionality only after the beta testers have tested a particular functionality of the product. For example, a developer may specify that a beta tester must configure and enable a working user registry before tape backup is permitted. User permission blocks are utilized to allow or disallow particular functions based on a beta enablement license as illustrated in Fig. 1.

Figure 1

A beta enablement license file is distributed to users wherein the beta enablement license file includes a list of functions and corresponding conditions for enablement. For example, a developer may choose to disable r...