SOFTWARE TESTING SYSTEM AND METHOD

• US 20150082279A1
• Filed: 09/13/2013
• Published: 03/19/2015
• Est. Priority Date: 09/13/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Jakobs, Daniel, Glaser, Marco
• Granted Patent: US 9,575,873 B2
• Time in Patent Office: Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3672 Test management

Abstract

A computer implemented system and method for testing code for implementation in web browsers, implements test class code defining test cases for testing operations on web applications implementable by different web browser types, and implements handler class code comprising code specific to each web browser and defining strategies to be used by test cases. The handler class code implements a handler interface and the test class code uses the handler interface to identify the methods to be used for test cases. A non-transient storage medium stores code for a handler template supporting different web browser types for use in a test environment, the code comprising code to identify browser specific strategies for implementation in the test environment; code to implement a strategy support interface for use by a handler factory to select a handler instance; and code to implement a handler interface for use by a test case to identify methods for testing web browser functions.

Claims

1. A software testing system for testing code for implementation in web browsers, the system comprising:

code memory storing computer code; and

a processor for reading the computer code in the code memory and executing the computer code;

wherein the computer code stored in the code memory comprises;

test class code defining test cases for testing operations on web applications implementable by different web browser types, and

handler class code comprising code specific to each web browser type and defining strategies to be used by test cases,

wherein the handler class code is adapted to implement a handler interface and the test class code is adapted to use the handler interface to identify the methods to be used for test cases.

2. A software testing system according to claim 1, wherein the handler class code is adapted to implement a strategy support interface defining strategies to be implemented dependent upon the web browser type, and the computer code stored in the code memory includes handler factory class code used by the test class code to obtain an instance of a handler class code by determining the web browser type being executed and by reference to the strategy support interface.

3. A software testing system according to claim 1, wherein the computer code stored in the code memory includes strategy class code adapted to implement the handler class code.

4. A software testing system according to claim 1, wherein the handler class code comprises inner class code defining the strategies to be used for each web browser type.

5. A software testing system according to claim 2, wherein the handler factory class code is adapted to determine the web browser type using a web browser driver.

6. A software testing system according to claim 1, wherein the computer code for implementation in web browsers comprises user interface code.

7. A software testing system according to claim 1, wherein the computer code stored in the code memory includes a web browser testing platform providing an environment for implementation of the test class code and the handler class code.

8. A software testing system according to claim 7, wherein the web browser testing platform comprises SAP Selenium.

9. A computer implemented method of testing code for implementation in web browsers, the method comprising:

implementing test class code defining test cases for testing operations on web applications implementable by different web browser types, and

implementing handler class code comprising code specific to each web browser type and defining strategies to be used by test cases,

wherein the handler class code implements a handler interface and the test class code uses the handler interface to identify the methods to be used for test cases.

10. A computer implemented method according to claim 9, wherein the handler class code implements a strategy support interface defining strategies to be implemented dependent upon the web browser type, the method including implementing handler factory class code used by the test class code to obtain an instance of a handler class code by determining the web browser being executed and by reference to the strategy support interface.

11. A computer implemented method according to claim 9, including implementing strategy class code to implement the handler class code.

12. A computer implemented method according to claim 9, wherein the handler class code comprises inner class code defining the strategies to be used for each web browser type.

13. A computer implemented method according to claim 10, wherein the handler factory class code determines the web browser type using a web browser driver.

14. A computer implemented method according to claim 9, wherein the code for implementation in web browsers comprises user interface code.

15. A computer implemented method according to claim 9, including implementing a web browser testing platform providing an environment for implementation of the test class code and the handler class code.

16. A computer implemented method according to claim 15, wherein the web browser testing platform comprises SAP Selenium.

17. A non-transient storage medium storing computer code for a handler template supporting different web browser types for use in a test environment, the computer code comprising:

computer code to identify browser specific strategies for implementation in the test environment;

computer code to implement a strategy support interface for use by a handler factory to select a handler instance; and

computer code to implement a handler interface for use by a test case to identify methods for testing web browser functions.

18. A non-transient storage medium according to claim 17, wherein the computer code includes computer code to identify that the handler extends an abstract handler used in the test environment.

19. A non-transient storage medium according to claim 17, wherein the handler template defines a handler class, and the computer code to identify specific strategies comprises inner classes.

20. A non-transient storage medium according to claim 17, wherein the test environment comprises SAP Selenium.