Making production data available for testing in a non-production environment

• US 9,846,635 B2
• Filed: 03/18/2016
• Issued: 12/19/2017
• Est. Priority Date: 03/18/2016
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Barjaktarovic, Milos
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Luu, Cuong V
• Application Number:
  US15/075,014
• Publication Number:
  US 20170270037A1
• Time in Patent Office: 641 Days
• CPC Class Codes: G06F 11/321 Display for diagnostics, e.g. diagnostic result display, self-test user interface
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

The technology disclosed relates to systems and methods usable for developing and testing dashboards with production data in non-production environments including a development server with APIs interposed between a development app and a production server, providing development access to production data before deployment into the production environment. The disclosed development server includes an app server that serves a development app in response to a request from a developer device; and exposes development APIs that mirror production APIs of the production server, and relay of messages between the development APIs and the production APIs. The development server replicates access to production server APIs relied on to retrieve and process time series data from a data store, the replication including access to development server APIs that mirror relative addressing of production APIs. Users can select among reviewed and approved dashboards, and can select to deploy the selected dashboards to the production server.

Claims

1. A method of making production data available from a production server for development testing, including:

providing a development server code, including

an app server code that, when run on a processor,

serves a development app that is a modified version of a production app, in response to a request from a developer device, wherein the development app includes replication of access to production server application programming interfaces (APIs) used to retrieve and process time series data from a data store, the replication including access to development server API'"'"'s that mirror relative addressing of production APIs; and

exposes development APIs that mirror production APIs of the production server and relay selected messages between the development app and the production server; and

a code manager that, when run on the processor, accesses development code definitions in a persistent development code store, in response to a request from the development app;

receiving at least one data assembly and rendering request from a development server that includes or references a definition of data assembly and rendering requirements;

processing each data assembly and rendering request against the data store; and

returning results of the processing via the development server.

2. The method of claim 1, further including a deployment manager that when run on the processor that accesses development code in the persistent development code store, deploys selected development code to the production server, in response to a request from the development app.

3. The method of claim 1, further including the production server receiving from the development server code, one or more data transformation requests that include a definition of data transformation requirements.

4. The method of claim 1, wherein the development code definitions in the persistent development code store are development code definitions of dashboards and are expressed in JSON or XML.

5. The method of claim 1, wherein the results returned via the development server from the processing include a graphic that illustrates the data assembled in response to the data assembly and rendering request.

6. The method of claim 1, wherein the results returned via the development server from the processing include data values assembled in response to the data assembly and rendering request, adapted for rendering by the development app.

7. A development server, including:

a processor, memory coupled to the processor, the processor coupled in communication with a persistent development code store that holds development code;

the processor coupled in communication with a production server;

an app server running on the processor that

serves a development app that is a modified version of a production app, in response to a request from a developer device; and

exposes development application programming interfaces (APIs) that mirror production APIs of the production server, and relay messages between the development APIs and the production APIs;

a code manager running on the processor that accesses the development code in the persistent development code store, in response to a request from the development app; and

the development app including;

a user interface for selection among development code definitions of dashboards; and

replication of access to production server APIs used to retrieve and process time series data from a data store, the replication including access to development server APIs that mirror relative addressing of production APIs.

8. The development server of claim 7, further including the app server running on the processor establishing a session by authenticating a developer to the production server.

9. The development server of claim 7, further including a deployment manager running on the processor that deploys selected development code to the production server, in response to a request from the development app.

10. The development server of claim 7, further including a user interface for selection of deployment of a development code definition to the production server.

11. The development server of claim 7, wherein the development code definitions of the dashboards are expressed in JSON or XML.

12. A method of making production data available for development testing, including:

at a development server;

receiving an app request from a developer device and serving a development app that is a modified version of a production app, wherein the development app;

processes user selection among development code definitions of dashboards in a persistent development code store; and

replicates access to a production server and production server application programming interfaces (APIs) used to retrieve and process time series data from a data store, the replication including access to development server APIs mirroring relative addressing of production APIs of the production server to implement access to data assembly from a production data store, and relaying messages between the development APIs and the production APIs;

receiving at a development API a preview request from the development app to preview at least one data assembly and rendering request;

forwarding the request and a dashboard code definition to the production server at a production API replicated by the development API that received the preview request; and

receiving from the production server and causing display, at the developer device, of results from the processing.

13. The method of claim 12, wherein the results received from the production server include a graphic that illustrates the data assembled in response to the preview request.

14. The method of claim 12, wherein the results received from the production server include data values assembled in response to the preview request, adapted for rendering at the developer device.

15. The method of claim 12, wherein the developer device includes an app or browser.

16. The method of claim 12, wherein the development API includes a user interface for selection of deployment to the production server of the development code.

17. The method of claim 12, wherein the persistent development code store uses one of JSON or XML to represent development code definitions of dashboards.

18. A development server code, stored in a non-transitory computer readable medium, including instructions executable on a processor that implement:

an app server that

serves a development app that is a modified version of a production app from a production server, in response to a request from a developer device, wherein the development app includes replication of access to production server application programming interfaces (APIs) used to retrieve and process time series data from a data store, the replication including access to development server API'"'"'s that mirror relative addressing of production APIs,

exposes development APIs that mirror production APIs of the production server that implement access to data assembly from a production data store, and relay selected messages between the development app and the production server; and

returns results from the processing to a developer device;

wherein the production APIs process requests for data assembly and rendering, accompanied by dashboard code definitions; and

a code manager that accesses development code in a persistent development code store, in response to a request from the development app.

19. The development server code of claim 18, stored in the non-transitory computer readable medium, further including a deployment manager that deploys selected development code to the production server, in response to a request from the development app.

20. The development server code of claim 18, stored in the non-transitory computer readable medium, further including a deployment manager including a user interface for selection of deployment to the production server of a selected development code definition.

21. The development server code of claim 18, stored in the non-transitory computer readable medium, wherein the returned results include a graphic that illustrates the data assembled in response to the data assembly and rendering request.

22. The development server code of claim 18, stored in the non-transitory computer readable medium, wherein the results returned via the development server from the processing include data values assembled in response to the data assembly and rendering request, adapted for rendering by the development app.

23. A development app code, stored in a non-transitory computer readable medium, the development app code including instructions executable on a processor that implement:

a development app that is a modified version of a production app from a production server, wherein the development app includes replication of access to production server application programming interfaces (APIs) used to retrieve and process time series data from a data store, the replication including access to development server API'"'"'s that mirror relative addressing of production APIs, and wherein the development app includes;

reference to development APIs of the development server that mirror the production APIs of the production server that implement access to data assembly from a production data store and relay messages between the development app and the production server;

wherein the production APIs process requests for data assembly and rendering, accompanied by dashboard code definitions, against a production data store;

access to a code manager running on the development server that accesses development code in a persistent development code store, in response to a request from the development app; and

access to a deployment manager that deploys selected development code from the persistent development code store to the production server, in response to a request from the development app.

24. The development app code of claim 23, stored in the non-transitory computer readable medium, wherein the deployment manager includes a user interface for selection of deployment to the production server, of selected development code definitions.