IP Library Granted Patent US 9,372,787
Granted Patent B2
US 9,372,787 · App. 13/942,337 · Granted Jun 21, 2016

System and method for automating testing

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,372,787
App. No.
13/942,337
Granted
Jun 21, 2016
Kind
B2
Abstract

According to some embodiments, a method and apparatus are provided to receive browser automation code to automatically test a software application executed in a web browser and receive a first parameter to indicate a first type of web browser and a second parameter to indicate a second type of web browser. The browser automation code is executed in the first type of web browser and the browser automation code is executed in the second type of web browser.

Claims (33)

1. A method to automate software testing without changing browser automation code, the method comprising:

receiving browser automation code to automatically test a software application executed in a web browser, the browser automation code comprising computer code that defines a specific sequence of events for testing the software application;

receiving a first parameter to indicate a first type of web browser;

executing, via a processor, the browser automation code in the first type of web browser via a framework comprising one or more object classes that interfaces between the browser automation code and the first type of web browser by emulating binaries associated with the first type of web browser based on the received first parameter, where executing the browser automation code in the first type of web browser comprises creating, via the one or more object classes, a first browser specific runtime environment to communicate between the emulated binaries and the browser automation code, and where the browser automation code executed in the first type of web browser is the received browser automation code;

receiving a second parameter to indicate a second type of web browser; and

executing the browser automation code in the second type of web browser via the framework that interfaces between the browser automation code and the second type of web browser by emulating binaries associated with the second type of web browser based on the received second parameter where the browser automation code executed in the second type of web browser is the received browser automation code, where executing the browser automation code in the second type of web browser comprises creating, via the one or more object classes, a second browser specific runtime environment to communicate between the emulated binaries and the browser automation code.

2. The method of claim 1 , wherein the specific sequence of events comprise a combination of (i) radio buttons or check boxes to activate, (ii) forms to be filled out or (iii) sequences of text to be input.

3. The method of claim 1 , wherein the framework program is based on an object-oriented computer programming language and comprises a class to create drivers associated with the received first parameter and second parameter.

4. The method of claim 1 , wherein the received first parameter and second parameter are stored in a configuration file.

5. The method of claim 1 , wherein a first of the one or more object classes is to emulate binaries associated with the first type of web browser and a second of the one or more object classes is to emulate binaries associated with the second type of web browser.

6. A non-transitory computer-readable medium comprising instructions that when executed by a processor perform a method to automate software testing without changing browser automation code, the method comprising:

receiving browser automation code to automatically test a software application executed in a web browser, the browser automation code comprising computer code that defines a specific sequence of events for testing the software application;

receiving a first parameter to indicate a first type of web browser;

executing, via a processor, the browser automation code in the first type of web browser via a framework comprising one or more object classes that interfaces between the browser automation code and the first type of web browser by emulating binaries associated with the first type of web browser based on the received first parameter, where executing the browser automation code in the first type of web browser comprises creating, via the one or more object classes, a first browser specific runtime environment to communicate between the emulated binaries and the browser automation code, and where the browser automation code executed in the first type of web browser is the received browser automation code;

executing the browser automation code in the second type of web browser via the framework that interfaces between the browser automation code and the second type of web browser by emulating binaries associated with the second type of web browser based on the received second parameter where the browser automation code executed in the second type of web browser is the received browser automation code, where executing the browser automation code in the second type of web browser comprises creating, via the one or more object classes, a second browser specific runtime environment to communicate between the emulated binaries and the browser automation code.

7. The medium of claim 6 , wherein the browser automation code is interfaced with a framework program to communicate with the first type of web browser and the second type of web browser.

8. The medium of claim 6 , wherein the specific sequence of events comprise a combination of (i) radio buttons or check boxes to activate, (ii) forms to be filled out or (iii) sequences of text to be input.

9. The medium of claim 7 , wherein the framework program is based on an object-oriented computer programming language and comprises a class to create drivers associated with the received first parameter and second parameter.

10. The medium of claim 7 , wherein the received first parameter and second parameter are stored in a configuration file.

11. The medium of claim 6 , wherein a first of the one or more object classes is to emulate binaries associated with the first type of web browser and a second of the one or more object classes is to emulate binaries associated with the second type of web browser.

12. An apparatus comprising:

a processor; and

a non-transitory computer-readable medium comprising instructions that when executed by a processor perform a method to automate software testing without changing browser automation code, the method comprising:

receiving browser automation code to automatically test a software application executed in a web browser, the browser automation code comprising computer code that defines a specific sequence of events for testing the software application;

receiving a first parameter to indicate a first type of web;

executing, via the processor, the browser automation code in the first type of web browser via a framework comprising one or more object classes that interfaces between the browser automation code and the first type of web browser by emulating binaries associated with the first type of web browser based on the received first parameter, where executing the browser automation code in the first type of web browser comprises creating, via the one or more object classes, a first browser specific runtime environment to communicate between the emulated binaries and the browser automation code, and where the browser automation code executed in the first type of web browser is the received browser automation code;

executing the browser automation code in the second type of web browser via the framework that interfaces between the browser automation code and the second type of web browser by emulating binaries associated with the second type of web browser based on the received second parameter where the browser automation code executed in the second type of web browser is the received browser automation code, where executing the browser automation code in the second type of web browser comprises creating, via the one or more object classes, a second browser specific runtime environment to communicate between the emulated binaries and the browser automation code.

13. The apparatus of claim 12 , wherein the browser automation code is interfaced with a framework program to communicate with the first type of web browser and the second type of web browser.

14. The apparatus of claim 13 , wherein the framework program is based on an object-oriented computer programming language and comprises a class to create drivers associated with the received first parameter and second parameter.

15. The apparatus of claim 14 , wherein the framework program creates a runtime environment to communicate between the created drivers and the browser automation code.

16. The apparatus of claim 12 , wherein the specific sequence of events comprise a combination of (i) radio buttons or check boxes to activate, (ii) forms to be filled out or (iii) sequences of text to be input.

17. The apparatus of claim 12 , wherein the received first parameter and second parameter are stored in a configuration file.

18. The apparatus of claim 12 , wherein a first of the one or more object classes is to emulate binaries associated with the first type of web browser and a second of the one or more object classes is to emulate binaries associated with the second type of web browser.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 23, 2016
From: SAP SE
To: SAP PORTALS ISRAEL LTD.
Reel/Frame 038685/0173 →
CHANGE OF NAME Recorded Aug 26, 2014
From: SAP AG
To: SAP SE
Reel/Frame 033625/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 15, 2013
From: SAAR, ASAF; SUDKOVICH, ALEX; HRISTOV, GEORGI; SREERANGARAJU, SREEVATSA
To: SAP AG
Reel/Frame 030799/0773 →