QTP的101宗罪

 

QTP大牛Tarun Lalwani列举了QTP的101个不足：

http://knowledgeinbox.com/articles/qtp/general/101-limitationsenhancement-for-qtp/

 

其中涵盖了Object Spy、IDE、对象库及管理、脚本编写、AOM、Recovery Scenarios、测试报告、CheckPoint

 

其中一些是长期以来广大QTP爱好者深恶痛绝的，例如不能同时打开多个脚本进行编辑。

 

Object Spy Enhancements
1. Object spy to have an option to export all the objects in hierarchy with their properties and methods to a XLS/XML file. And also to have an option to reload this offline. This feature would help for others to analyze a object recognition remotely
2. Object spy to have the ability to run without QTP. Currently object spy can only be loaded through QTP
3. Object spy to have an option to disable the Auto spy. Currently hovering on any object displays it properties without the need to click the object. This at time gives poor performance while spying objects
4. Currently Object Spy button gets disabled when the script is run, one has to launch object repository and then launch Object Spy from there. The Object Spy should enable directly when the script is run
5. Object Spy Automation capability, so other tools can leverage the same and automate the OR creation based on custom rules
6. Object spy to have capability to spy on dynamically created objects. E.g. – The search suggestion box on Google
7. Object Spy to have facility to compare two different objects and show the differences
8. Object Spy to support XPaths for identifying objects

IDE Enhancement
9. Ability to open multiple scripts at one time
10. Project explorer with capability to create folder and organize resource inside them (library files, ORs, recovery scenarios) in them
11. Improved Intellisense for objects created through DotNetFactory
12. Intellisense for VBScript classes
13. Function folding and code folding in the IDE
14. Transition from Design mode to Run mode causes too many flickers in the IDE UI. This needs to be smooth
15. Ability to view code for Test flow in Expert view. This is currently only possible through Keyword view
16. Design time non-syntax error check for issues like Duplicate variable declaration etc
17. Intellisense of current associated libraries in all Libraries. Currently if Lib1 and Lib2 are associated with a Test. The Lib1 will only show Intellisense for Lib1 and not for Lib2. The Test will show Intellisense for both Lib1 and Lib2. This creates difficulty when Lib2 functions need to be called in Lib1
18. Custom Intellisense for parameters. E.g. if a framework creates GetObject method and that takes in keyword which is loaded from a external excel/XML file then to be able to provide Intellisense with those keyword
19. Script workflow diagram, something similar to keyword view but not at statement level but at function and action in flows
20. Ability to search called Actions in current script and go to the same. Current UI is very unfriendly in case too many actions are called in the script
21. Ability to specify default run results directory and avoid the dialog for run results location for every run. This gets very annoying when debugging the script
22. Input Parameters tab in Run dialog should remember the history of values used last time. Currently if Test/Component parameters are used and for debugging the same parameters value are updated before start the run, these values are lost next time run is initiated. This causes a lot of value update every time the script needs to be run for debugging
23. Ability to pause recording, currently when recording starts it can only be stopped. Having a feature to pause recording would help a lot

Object Repository Enhancements
24. Ability to create and load OR’s from QTP script itself
25. Ability to load Shared ORs dynamically to all the Actions. Currently RepositoriesCollection.Add methods adds the SOR to the current Action only and not other actions
26. Changes made through SetTOProperty in one Action does not get propagated to Next Action
27. Ability to enumerate all child objects present in the OR for a specified object
28. Ability to specify nickname for Objects. This would help get a complete object hierarchy through just the nick name
29. Ability to directly record objects into the SOR

Object Repository Manager Enhancements
30. Ability to load and save directly to OR in XML format
31. Ability for multiple users to access the Shared OR at the same time for updating
32. Export/Import of Checkpoints from one SOR to another
33. Merging of SOR’s to an existing SOR. Currently when two SOR are merged, the merged SOR needs to be saved as a different file
34. Ability to update code when conflict resolution renames object during SOR merge. In case object A and B are merged and name A is chosen over B, all scripts using name B needs to be updated manually

Scripting Enhancements
35. More options for other scripting languages i.e. JScript, VB.NET, C#.NET etc…
36. Support for start and finish events in Action and Test. E.g. – Test_Init, Test_Terminate, Action_Init, Action_Terminate. Currently this can be achieved through use of class but it would be easier for people to use if the functionality is built-in
37. Ability to execute specified VBScript even before the test execution starts. This script would run outside QTP and would help make changes to QTP settings that cannot be done during run-time. This would help in overcoming limitations like Libraries cannot be associated at run-time
38. Ability to execute specified VBScript even after the test execution starts. This script would run outside QTP and would help perform post execution code. This would be helpful in scenarios like sending email with the report
39. Ability to create error handler functions which are automatically called when an error occurs
40. Performance improvement when using Descriptive programming when compared to Object Repository usage
41. Ability to Debug libraries loaded during run-time using Execute, ExecuteGlobal and ExecuteFile
42. Ability to unload a library at run-time
43. Ability to register generic functions for any object type. Currently RegisterUserFunc can only be used to register the method for a single object type. So if a new Set method is created then multiple RegisterUserFunc statements need to be written. QTP should provided some way to use a pattern or something to apply the same method to multiple object types
44. Ability to Unlock a locked system from within the code
45. Ability to prevent screen locking during the execution
46. Ability to debug error which occurs during terminations of script. Currently any errors that occur during the termination of the script cannot be debugged and launches
47. Ability to Enumerate current Action parameters
48. Ability to Enumerate current Test Parameters
49. Ability to Enumerate current Environment parameters
50. Ability to Export environment variables to XML in code
51. Ability to save data directly to Design time data table
52. Ability to load Excel 2007 files into data table
53. Ability to Encrypt the script code
54. Ability to password protect the scripts
55. Ability to save the list of libraries open and the libraries to automatically open when opening the script
56. Ability to save the breakpoints and bookmarks with the script
57. Ability to move a script from write mode to read-only mode. Currently Enable editing button only enables read-only to write mode transition in tests/components/libraries and not vice-versa
58. Ability to execute in thread. Even one thread would do
59. Ability to call Windows API which require structures
60. Ability to Load/Unload add-ins at run-time
61. Add-in SDK documentation to create new add-ins
62. Ability to use a external excel file directly as a DataTable and have access to all the excel objects as well
63. Ability to pause/break a script. Similar to Debug.Assert method in VB
64. Ability to reconnect to QC automatically when the connect times out to the server
65. Built-in support for Web 2.0 and AJAX
66. Ability to call one Test from another test
67. Auto include of SOR and Associated libraries when calling a external action present in some other script
68. Ability to clear session cookies of a browser without closing the browser
69. Ability to get the stack trace in the code in case of an error
70. Improvement in error messages in case of general error messages
71. Ability to get the current function name from inside the function
72. Ability to get the time taken by a transaction when using Services.EndTransaction
73. Ability to do OCR on images (captcha) and convert them to text

QTP AOM Enhancements
74. Ability to open Business process script in QTP
75. Ability to open/close library file in UI using AOM
76. Ability to create a library file through AOM and add code to the same
77. Ability to create, open and modify a BPT Application area through AOM
78. Ability to set/delete breakpoints in IDE using AOM
79. Ability to change any option at run-time and having the change impacted instantly
80. Ability to convert a BPT component to a normal test using AOM and through UI as well

Recovery Scenarios Enhancements
81. Recovery scenarios (RS) to run in a separate thread. Currently recovery scenarios run in the same thread as QTP. This causes recovery scenarios to be useless in case a Modal dialog blocks QTP
82. Option to stop chaining in recovery scenarios. Currently if RS1 and RS2 both match the trigger criteria then both of the scenarios are executed. There is no way to specify that RS2 should not be executed if RS1 is executed
83. Currently there is no way to enumerate recovery scenarios present in a File
84. Recovery scenarios don’t work when they are associated at run-time
85. Ability to test the RS trigger from the UI. This would help debug in debugging the issues when recovery scenario does not get fired

Test Reporting Enhancements
86. Ability to create reports in different format. Excel, Word, HTML etc…
87. Reporting of errors or failure in different categories and priority. E.g. – Reporting a error with severity, priority and category (Application, Script, Validation, Checkpoint)
88. Exact location of the error in the script. This should include the line of code, error number, error statement
89. Direct ability to send report to a specified list of email addresses when the test end
90. Currently the reports can only be viewed through QTP reporter viewer and cannot be viewed on machines without this tool. Report should be made completely Web compatible so that I can be viewed in any browser in the same way it is displayed in report viewer
91. Ability to view status of current Action. Currently Reporter.RunStatus only provides the status of whole test and not for current action
92. Ability to enumerate the current status from within a Test i.e. Actions executed with details, checkpoints executed with details, recovery scenarios executed with details
93. Hosting web server to capture and display script status in batch
94. Ability to report to a existing result file
95. Ability to override the Action Name in reports
96. Ability to specify the time zone to be used in reports
97. Ability to specify the results path during the run

Checkpoint Enhancements
98. Ability to alter properties of all checkpoints during run-time. E.g. Expected bitmap of a bitmap checkpoint, expected values of a Table/DB checkpoint etc
99. Ability to create checkpoints at run-time
100. Ability to load checkpoints from a external file at run-time
101. Ability to enumerate all checkpoints present in current script