Salesforce Com, Inc.

Richard Unger

Taggart Matthiesen

Simon Y Wong

Andrew Waite

Fiaz Hossain

Peter S Wisnovsky

Alan Ballard

K Sagar Wanaselja

Craig David Weissman

Described herein are means for debugging byte code in an on-demand service environment system including a system for simulating execution debug in a multi-tenant database environment. Such means may include: receiving a request at a web-server of the system, determining one or more trace preferences are active for the request, sending the request to a logging framework communicatively interfaced to the multi-tenant database implementation, processing the request via the logging framework, and capturing at least a portion of the execution data emitted responsive to execution of the plurality of events for use in simulating execution debug of the events. Other related embodiments are additionally described.

Methods and systems for debugging bytecode in an on-demand service environment

In accordance with disclosed embodiments, there are provided methods, systems, and apparatuses for creating a data silo and testing with a data silo including, for example, initiating a test sequence against a production database within the host organization, in which the test sequence specifies: a) new data for insertion into the production database during the test sequence, and b) one or more test queries against the production database during the test sequence; performing a database transaction to insert the new data into the production database without committing the new data to the production database; recording names of one or more objects corresponding to the inserted new data, the one or more objects created as part of the transaction to insert the new data into the production database within a transaction entity object map; modifying the one or more test queries specified by the test sequence to no longer query against the production database by substituting the one or more test queries with references to the names of the one or more objects in operating memory separate from information stored within the production database; and executing the one or more modified test queries. Other related embodiments are disclosed.

Testing data silo

Disclosed herein are techniques for testing a page. In some implementations, an intermediate representation of a page is created. The page may be defined by a page description implemented in a markup language. The page description may refer to data accessible via a data model. The intermediate representation may include at least a portion of the data accessible via the data model. The intermediate representation may be capable of being rendered to create a rendered page. The rendered page may be capable of being displayed on a display device. A determination may be made as to whether a test value for a portion of the intermediate representation matches an expected value for the portion of the intermediate representation. When the test value does not match the expected value, an indication of an error may be stored.

Test framework of visual components in a multitenant database environment

In accordance with disclosed embodiments, there are provided methods, systems, and apparatuses for creating a data silo and testing with a data silo including, for example, initiating a test sequence against a production database within a host organization, wherein the test sequence specifies: (a) new data for insertion into the production database during the test sequence and (b) one or more queries for execution against the production database during the test sequence. Such a method further includes inserting the new data into the production database; recording one or more row IDs corresponding to the inserted new data; injecting a test context filter into the one or more queries based on the one or more row IDs; and executing the one or more queries against the production database.

Disclosed herein are techniques for compiling a procedure for testing a page. In some implementations, a component definition for a component instance referred to in computer programming language instructions defining a test procedure for testing a page may be received. The page may be defined by a page description implemented in a markup language. The page description may include a reference to a first portion of a component instance. Compiled wrapper code operable to simulate the presence of the component instance may be generated. The compiled wrapper code may represent the first portion of the component instance referenced in the page description. A compiled test procedure may be generated based on the computer programming language instructions. The compiled test procedure may include the compiled wrapper code. The compiled test procedure may be capable of being executed to perform the test procedure.

In accordance with embodiments disclosed herein, there are provided systems, devices, and methods for testing methods in a multi-tenant database environment, including, for example, hosting a plurality of customer codebases within a host organization, where each of the plurality of customer codebases includes a plurality of operational statements and one or more test methods. Such a method further includes generating a first test result set by executing the one or more test methods associated with each of the plurality of customer codebases against a production release codebase of the host organization; generating a second test result set by executing the one or more test methods associated with each of the plurality of customer codebases against a pre-release codebase of the host organization; and identifying errors associated with the pre-release codebase based on a comparison of the first test result set and the second test result set.

Methods and systems for testing methods in a multi-tenant database environment

In accordance with embodiments, there are provided mechanisms and methods for providing custom settings in an on-demand service environment. In an embodiment and by way of example, a method providing custom settings in an on-demand service environment is provided. The method embodiment includes naming the custom object, creating fields for the custom object, assigning a behavior for each field, setting the custom object to a specified type, and if the custom object is of a hierarchical type, then assigning permissions to users with regarding the created fields.

Growing community of inventors

Seattle, WA, United States of America

Richard Unger