Computer implemented systems and methods for testing the usability of a software application

• US 20070209010A1
• Filed: 03/01/2006
• Published: 09/06/2007
• Est. Priority Date: 03/01/2006
• Status: Abandoned Application

• Current Assignee: SAS Institute Incorporated
• Original Assignee: SAS Institute Incorporated
• Inventors: West, Ryan
• Application Number:
  US11/365,649
• Publication Number:
  US 20070209010A1
• Time in Patent Office: Days
• US Class Current: 715/762
• CPC Class Codes: G06F 11/3414 Workload generation, e.g. scripts, playback
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• 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
• CPC Class Codes: G06F 2201/805 Real-time
• CPC Class Codes: G06F 2201/86 Event-based monitoring

Abstract

In accordance with the teachings described herein, systems and methods are provided for testing the usability of a software application. A test interface may be provided that executes independently of the software application under test. A task may be assigned via the test interface that identifies one or more operations to be performed using the software application under test. One or more inputs may be received via the test interface to determine if the task was performed successfully.

Claims

1. A method for testing the usability of a software application, comprising:

providing a test interface that executes independently of the software application under test;

assigning a task via the test interface, the task identifying one or more operations to be performed using the software application under test; and

receiving one or more inputs via the test interface to determine if the task was performed successfully.

2. The method of claim 1, wherein there is no programmatic interaction between the test interface and the software application under test.

3. The method of claim 1, wherein the one or more inputs include a task completion input for indicating that the task has been successfully performed.

4. The method of claim 3, further comprising:

providing a validation question via the test interface, wherein the one or more inputs include an answer to the validation question which verifies that the task was performed successfully.

5. The method of claim 4, wherein the validation question requests data that may be determined upon successful completion of the task, and wherein the answer to the validation question provides the requested data.

6. The method of claim 1, wherein the one or more inputs include a task failure input for indicating that the task has not been successfully performed.

7. The method of claim 6, further comprising:

in response to receiving the task failure input, providing instructions for performing the task.

8. The method of claim 7, further comprising:

receiving an additional input that identifies one or more reasons why the task was not successfully performed.

9. The method of claim 8, wherein the additional input identifies which one or more of the task operations resulted in the task not being successfully performed.

10. The method of claim 1, further comprising:

receiving a begin task input via the test interface indicating a start of the task;

receiving an end task input via the test interface indicating an end of the task; and

determining an amount of time spent on the task based on the begin task input and the end task input.

11. The method of claim 10, wherein the end task input is a task completion input indicating that the task was successfully performed.

12. The method of claim 10, wherein the end task input is a task failure input indicating that the task was not successfully performed.

13. The method of claim 1, wherein the test interface is provided over a computer network.

14. The method of claim 13, wherein the test interface is a web-based application.

15. The method of claim 14, wherein the software application under test is not web-based.

16. The method of claim 1, wherein the test interface is provided by a testing software application, the testing software application and the application under test executing on the same computer.

17. An automated usability testing system, comprising:

a usability testing program that provides a test interface for use in testing the usability of a software application, the usability testing program being configured to execute independently of the software application under test;

the usability testing program being configured to display a task via the test interface, the task identifying one or more operations to be performed using the software application under test; and

the usability testing program being further configured to receive one or more inputs via the test interface to determine if the task was performed successfully.

18. The automated usability testing system of claim 17, wherein there is no programmatic interaction between the usability testing program or the test interface and the software application under test.

19. The automated usability testing system of claim 18, wherein the usability testing program does not receive event data recorded in connection with the operation of the software application under test.

20. The automated usability testing system of claim 17, further comprising:

test configuration data stored on a computer readable medium, the test configuration data for use by the usability testing program in displaying the task.

21. The automated usability testing system of claim 17, wherein the usability testing program executes on a first computer and the software application under test executes on a second computer, the first computer being coupled to the second computer via a computer network, and the test interface being displayed on the second computer.

22. The automated usability testing system of claim 17, wherein the usability testing program and the software application under test execute on the same computer.

23. The automated usability testing system of claim 17, wherein the one or more inputs include a task completion input for indicating that the task has been successfully performed.

24. The automated usability testing system of claim 23, wherein the test interface includes a task completion field for inputting the task completion input.

25. The automated usability testing system of claim 24, wherein the task completion field is a graphical button.

26. The automated usability testing system of claim 23, wherein the usability testing program is further configured to provide a validation question via the test interface, wherein the one or more inputs include an answer to the validation question which verifies that the task was performed successfully.

27. The automated usability testing system of claim 26, wherein the test interface includes a textual input field for inputting the answer to the validation question.

28. The automated usability testing system of claim 26, wherein the validation question requests data that may be determined upon successful completion of the task, and wherein the answer to the validation question provides the requested data.

29. The automated usability testing system of claim 17, wherein the one or more inputs include a task failure input for indicating that the task has not been successfully performed.

30. The automated usability testing system of claim 29, wherein the test interface includes a task failure field for inputting the task failure input.

31. The automated usability testing system of claim 30, wherein the task failure field is a graphical button.

32. The automated usability testing system of claim 29, wherein the usability testing program is further configured to display instructions for performing the task in response to receiving the task failure input.

33. The automated usability testing system of claim 32, wherein the instructions are displayed separately from the test interface.

34. The automated usability testing system of claim 32, wherein the usability testing program is further configured to receive an additional input via the test interface to identify one or more reasons why the task was not successfully performed.

35. The automated usability testing system of claim 34, wherein the additional input identifies which one or more of the task operations resulted in the task not being successfully performed.

36. The automated usability testing system of claim 17, wherein the usability testing program is further configured to determine an amount of time spent on the task.

37. The automated usability testing system of claim 36, wherein the usability testing program is further configured to receive a begin task input via the test interface to indicate a start of the task, receive an end task input via the test interface to indicate an end of the task, and determine the amount of time spent on the task based on the begin task input and the end task input.

38. The automated usability testing system of claim 37, wherein the end task input is a task completion input indicating that the task was successfully performed.

39. The automated usability testing system of claim 38, wherein the test interface includes a begin task field for inputting the begin task input and includes a task completion field for inputting the task completion input.

40. The automated usability testing system of claim 39, wherein the begin task field and the task completion field are graphical buttons.

41. The automated usability testing system of claim 37, wherein the end task input is a task failure input indicating that the task was not successfully performed.

42. The automated usability testing system of claim 41, wherein the test interface includes a begin task field for inputting the begin task input and includes a task failure field for inputting the task failure input.

43. The automated usability testing system of claim 42, wherein the begin task field and the task failure field are graphical buttons.

44. The automated usability testing system of claim 17, wherein the usability testing program is configured to provide one or more additional test interfaces for use in testing the usability of one or more additional software applications.

45. The automated usability testing system of claim 44, further comprising:

one or more additional sets of test configuration data stored on one or more computer readable mediums, the additional sets of test configuration data for use by the usability testing program in providing the one or more additional test interfaces, wherein each additional set of test configuration data corresponds to one of the additional software applications under test.

46. A computer-readable medium having a set of software instructions stored thereon, the software instructions comprising:

first software instructions for providing a test interface that executes independently of-the software application under test;

second software instructions for assigning a task via the test interface, the task identifying one or more operations to be performed using the software application under test; and

third software instructions for receiving one or more inputs via the test interface to determine if the task was performed successfully.

47. The computer-readable medium of claim 46, wherein the one or more inputs include a task completion input for indicating that the task has been successfully performed, further comprising:

fourth software instructions for providing a validation question via the test interface, wherein the one or more inputs include an answer to the validation question which verifies that the task was performed successfully.

48. The computer-readable medium of claim 46, wherein the one or more inputs include a task failure input for indicating that the task has not been successfully performed, further comprising:

fourth software instructions for displaying instructions for performing the task in response to receiving the task failure input.

49. The computer-readable medium of claim 48 further comprising:

fifth software instructions for receiving an additional input that identifies one or more reasons why the task was not successfully performed.

50. The computer-readable medium of claim 46, further comprising:

fourth software instructions for receiving a begin task input via the test interface indicating a start of the task;

fifth software instructions for receiving an end task input via the test interface indicating an end of the task; and

sixth software instructions for determining an amount of time spent on the task based on the begin task input and the end task input.