System and method for testing an application

• US 20020188890A1
• Filed: 06/04/2002
• Published: 12/12/2002
• Est. Priority Date: 06/04/2001
• Status: Abandoned Application

• Current Assignee: Sentiat Technologies Incorporated
• Original Assignee: Sentiat Technologies Incorporated
• Inventors: Swartz, Jonathan, Shupps, Eric A., Wilson, Kirk H.
• Application Number:
  US10/161,879
• Publication Number:
  US 20020188890A1
• Time in Patent Office: Days
• US Class Current: 714/38
• CPC Class Codes: G06F 11/3414 Workload generation, e.g. scripts, playback
• CPC Class Codes: G06F 11/3447 Performance evaluation by modeling
• 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 2201/87 Monitoring of transactions
• CPC Class Codes: G06F 8/75 Structural analysis for program understanding

Abstract

A process can be used to test an application. In general, the process can include a transaction definition portion, a validation portion, and an optional modification portion. Unlike the conventional processes, the testing can be performed using “scriptless” transactions. The transaction definition may occur during navigation by a user through a network site while data regarding application is collected. Alternatively, a user may select transactable components or transactions from a list or a group of icons. In still another alternative, the transaction definition may be performed automatically using log files or component relationship data. Validation may be performed in-process or out-of-process to give greater flexibility. Modification may be performed manually or automatically. Also, modification may be performed after validation has started but before it is completed.

Claims

1. A process for testing an application, comprising:

generating a transaction definition for a transaction that can be performed using the application, wherein the transaction definition is not part of a script file; and

validating the transaction.

2. The process of claim 1, wherein generating a transaction definition further comprises navigating through a network site to sequentially step though portions of the network site accessed during the transaction itself.

3. The process of claim 1, further comprising identifying a first component within the application, wherein:

the first component is part, but not all, of a document; and

the first component is not a link.

4. The process of claim 3, further comprising identifying the first component as a first transactable component, wherein generating a transaction definition further comprises selecting the first transactable component.

5. The process of claim 4, wherein:

generating a transaction definition further comprises displaying information that comprises representations of a plurality of transactable components; and

the plurality of transactable components comprises the first transactable component.

6. The process of claim 4, further comprising:

identifying a second component within the application; and

determining relationship data between the first component and the second component,

wherein generating the transaction definition comprises generating the transaction definition using the relationship data.

7. The process of claim 1, further comprising accessing a log file for a network site, wherein generating the transaction definition is performed using information from the log file.

8. The process of claim 1, wherein generating the transaction definition comprises selecting the transaction by clicking on a representation of the transaction.

9. The process of claim 1, further comprising modifying the transaction.

10. The process of claim 9, wherein modifying is performed after validating starts but before validating is completed.

11. The process of claim 10, wherein after modifying, validating is continued without restarting validation from the beginning.

12. The process of claim 9, wherein modifying automatically changes the transaction definition, so that a step is added or removed from the transaction definition.

13. The process of claim 9, further comprising recording transaction versioning information.

15. The process of claim 14, wherein generating comprises navigating through a network site to sequentially step though portions of the network site accessed during the transaction itself.

16. The process of claim 14, further comprising identifying the first component as a first transactable component, wherein generating comprises selecting the first transactable component.

17. The process of claim 16, wherein:

generating further comprises displaying information that comprises representations of a plurality of transactable components; and

the plurality of transactable components comprises the first transactable component.

18. The process of claim 16, further comprising:

identifying a second component within the application; and

determining a relationship datum between the first component and the second component,

wherein generating comprises generating the transaction definition using the relationship datum.

19. The process of claim 14, further comprising accessing a log file for a network site, wherein generating is performed using information from the log file.

20. The process of claim 14, wherein generating comprises selecting the transaction by clicking on a representation of the transaction.

21. The process of claim 14, further comprising modifying the transaction.

22. The process of claim 21, wherein modifying is performed after validating starts but before validating is completed.

23. The process of claim 22, wherein after modifying, validating is continued without restarting validation from the beginning.

24. The process of claim 21, wherein modifying automatically changes the transaction definition, so that a step is added or removed from the transaction definition.

25. The process of claim 21, further comprising recording transaction versioning information.

26. The process of claim 14, wherein identifying comprises parsing the application.

28. The data processing system readable medium of claim 27, wherein the instruction for generating comprises an instruction to collect information as a user navigates through portions network of the site accessed during the transaction itself.

29. The data processing system readable medium of claim 27, wherein the code further comprises an instruction for identifying a first component within the application, wherein:

the first component is part, but not all, of a document; and

the first component is not a link.

30. The data processing system readable medium of claim 29, wherein the code further comprises an instruction for identifying the first component as a first transactable component, wherein the instruction for generating comprises an instruction for selecting the first transactable component.

31. The data processing system readable medium of claim 30, wherein:

the instruction for generating further comprises an instruction for displaying information that comprises representations of a plurality of transactable components; and

the plurality of transactable components comprises the first transactable component.

32. The data processing system readable medium of claim 30, wherein the code further comprises:

an instruction for identifying a second component within the application; and

an instruction for determining relationship data between the first component and the second component,

wherein the instruction for generating comprises an instruction for generating the transaction definition using the relationship data.

33. The data processing system readable medium of claim 27, wherein the code further comprises an instruction for accessing a log file for a network site, wherein the instruction for generating comprises an instruction to use information from the log file.

34. The data processing system readable medium of claim 27, wherein the instruction for generating comprises an instruction for receiving a click signal from a user, wherein the click signal corresponds to the transaction.

35. The data processing system readable medium of claim 27, wherein the code further comprises an instruction for modifying the transaction.

36. The data processing system readable medium of claim 35, wherein the instruction for modifying is executed after validating starts but before validating is completed.

37. The data processing system readable medium of claim 36, wherein after executing the instruction for modifying, validating is continued without restarting validation from the beginning.

38. The data processing system readable medium of claim 35, wherein the instruction for modifying is executed to automatically change the transaction definition, so that a step is added or removed from the transaction definition.

39. The data processing system readable medium of claim 35, wherein the code further comprises an instruction for recording transaction versioning information.

14. A process for testing an application, the process comprising:

identifying a first component within the application, wherein;

the first component is part, but not all, of a document; and

the first component is not a link;

generating a transaction definition for a transaction that can be performed using the application; and

validating the transaction.

27. A data processing system readable medium having code embodied therein, the code is designed to test an application, the code comprising:

an instruction for generating a transaction definition for a transaction that can be performed using the application, wherein the transaction definition is not part of a script file; and

an instruction for validating the transaction.

40. A process for testing an application, the data processing system readable medium comprising:

an instruction for identifying a first component within the application, wherein;

the first component is part, but not all, of a document; and

the first component is not a link;

an instruction for generating a transaction definition for a transaction that can be performed using the application; and

an instruction for validating the transaction.

41. The data processing system readable medium of claim 40, wherein the instruction for generating comprises an instruction to collect information as a user navigates through portions network of the site accessed during the transaction itself.

42. The data processing system readable medium of claim 40, wherein the code further comprises an instruction for identifying the first component as a first transactable component, wherein the instruction for generating comprises an instruction for selecting the first transactable component.

43. The data processing system readable medium of claim 42, wherein:

the instruction for generating further comprises an instruction for displaying information that comprises representations of a plurality of transactable components; and

the plurality of transactable components comprises the first transactable component.

44. The data processing system readable medium of claim 42, wherein the code further comprises:

an instruction for identifying a second component within the application; and

an instruction for determining a relationship datum between the first component and the second component,

wherein the instruction for generating comprises an instruction for generating the transaction definition using the relationship datum.

45. The data processing system readable medium of claim 40, wherein the code further comprises an instruction for accessing a log file for a network site, wherein the instruction for generating comprises an instruction to use information from the log file.

46. The data processing system readable medium of claim 40, wherein the instruction for generating comprises an instruction for receiving a click signal from a user, wherein the click signal corresponds to the transaction

47. The data processing system readable medium of claim 40, wherein the code further comprises an instruction for modifying the transaction.

48. The data processing system readable medium of claim 47, wherein the instruction for modifying is executed after validating starts but before validating is completed.

49. The data processing system readable medium of claim 48, wherein after the instruction for modifying is executed, validating is continued without restarting validation from the beginning.

50. The data processing system readable medium of claim 47, wherein the instruction for modifying automatically changes the transaction definition, so that a step is added or removed from the transaction definition.

51. The data processing system readable medium of claim 47, wherein the code further comprises an instruction for recording transaction versioning information.

52. The data processing system readable medium of claim 40, wherein the instruction for identifying comprises parsing the application.