Test Procedure Compiler for Multitenant UI Testing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In on-demand service environments, testing user interfaces is cumbersome due to the need for significant resources and time in installation, maintenance, and ensuring compatibility across different computer systems, leading to outdated software and compatibility issues.

Innovation Solution

A method for testing user interfaces in a multitenant database environment that allows for dynamic page rendering and testing without full rendering, using a test procedure compiler to simulate UI components and reduce computing load and storage space, enabling users to write test procedures at the page compiler level without modifying secure procedures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If full page rendering is performed for testing, then testing accuracy is improved, but computing load and storage space increase significantly

Engineering Contradiction:

Improvetesting accuracyVSAvoidcomputing load

Core Design Contradiction:

Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the essential UI component definitions and testing logic from the full page rendering process. The test procedure compiler compiles test procedures without requiring complete page rendering, separating the testing function from the full rendering pipeline to reduce computing load while maintaining testing accuracy.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary compilation of test procedures at the page compiler level before actual testing execution. This preliminary action prepares test data and validates test logic in advance, allowing testing to proceed without the overhead of full page rendering during the actual test execution phase.

Inventive Principle:

Principle #10Preliminary action

2Measurement precision

If full page rendering is performed for testing, then testing accuracy is improved, but storage space requirements increase

Engineering Contradiction:

Improvetesting accuracyVSAvoidstorage space

Core Design Contradiction:

Measurement precisionVSVolume of stationary object

Solution Approach 1:

The patent extracts only the necessary component definitions and test data from full page rendering. By storing only essential testing artifacts rather than complete rendered pages, the system maintains testing accuracy while significantly reducing storage space requirements.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates simplified copies of UI components for testing purposes rather than storing complete page renderings. These component-level copies contain only the information necessary for testing, reducing storage requirements while preserving testing functionality.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If users can modify secure procedures for testing, then testing flexibility is improved, but system security and stability deteriorate

Engineering Contradiction:

Improvetesting flexibilityVSAvoidsystem security

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the testing functionality from secure procedures by introducing a dedicated test procedure compiler. This separation allows users to write and execute test procedures in an isolated environment without granting access to or modification rights over secure system procedures, maintaining both flexibility and security.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The test procedure compiler acts as an intermediary between user test procedures and the underlying secure system. It provides users with flexible testing capabilities while preventing direct access to secure procedures, thus maintaining system security and stability.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Reliability

If traditional software installation and maintenance is performed across multiple computer systems, then software compatibility is improved, but time consumption and resource requirements increase

Engineering Contradiction:

Improvesoftware compatibilityVSAvoidtime consumption

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent implements a universal test procedure compiler that can execute testing across multiple computer systems and platforms. This single unified testing mechanism replaces the need for separate installation and maintenance procedures on each individual system, significantly reducing time consumption while maintaining compatibility across diverse environments.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS8959483B2Test framework of visual components in a multitenant database environment

Publication Date: 2015.02.17 SALESFORCE INC

AI summary

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.