RPT8.1新特性

RPT8.1下載地址：

http://www.ibm.com/developerworks/cn/downloads/r/rpt/

 

 

RPT8.1版本的新特性說明：

What's new in Rational Performance Tester 8.1 (HTTP)

New features in this release include the ability to set performance requirements; split a test; define variables within a test; add comments, add transactions, and change page names during recording; watch a virtual user during a test run, replay a virtual user after a run completes, and create reports that change color when a condition is satisfied.

This release of Rational® Performance Tester supports the following new features:

• You can add performance requirements to specify acceptable thresholds of performance and to validate service level agreements:
  • You can add performance requirements to tests or schedules. For more information, see Defining performance requirements in tests and Defining performance requirements in schedules.
  • You can create a Performance Requirement report, which shows which requirements passed and which failed. For more information, see Performance Requirements report.
  • You can place requirements on resource counters and performance measurements.
• You can split a test into smaller tests to make test more reusable and maintainable. For information on how to split a test, see Splitting a test.
• You can create test variables to share data among tests. For more information, see About test variables.
• You can easily select multiple test elements to view and modify their attributes. For more information, see Locating specific types of test elements.
• When recording HTTP tests using Internet Explorer or Firefox, you can add comments, add transactions, and change page names. For more information, see Annotating a test during recording.
• During a test or schedule run, you can view rendered HTTP pages and event logs for any virtual user. For more information, see Watching a virtual user during a test run and Watching a virtual user during a schedule run.
• You can replay a virtual user after a run is complete. For more information, see Replaying a virtual user after a run completes.
• You can create a transaction in a schedule as well as in a test. For more information, see Adding a transaction to a schedule.
• You can customize the colors that are used in charts and tables and create conditions that change the color when they are satisfied. For more information, see Setting custom and conditional report colors.
• HTTP response time calculation has improved. Therefore, test results might differ between this release and previous releases. Specifically, response time no longer includes page response times associated with a failing HTTP request. The only exception is when the failure is recorded and returned, and the request is not the primary request. Page response times that time out are always discarded. The response time also no longer includes HTTP requests that time out or return a status code in the range of 4XX (client errors) - 5XX (server errors).
• Percentile reports no longer depend on the test log level. This means that you can display them during a run.
• Percentile data is available for most response time counters.
• Other new features:
  • Data correlation is supported for most HTTP data in the JavaScript™ Object Notation (JSON) and Atom formats, which are commonly used in Web 2.0 and Representational state transfer (REST) applications.
  • Support for the PUT, DELETE, and HEAD methods has been added for HTTP so that applications using REST services can be tested.
  • Data transformations support correlation and datapools for binary HTTP data.
  • Transformers are supplied for generic binary data and for Java™ Serialized Objects.
  • You can now see HTTP binary data in the test editor.

 

主要是增加了在測試（Test）或排程（Schedule）中新增和定義效能需求的功能：

You can define performance requirements for a schedule to specify acceptable thresholds of performance and to validate service level agreements.

To define a performance requirement in a schedule:

1. In the Test Navigator, browse to the schedule and double-click it. The schedule opens.
2. In the Schedule Element Details area, click the Performance Requirements tab, and select Enable Performance Requirements. The page contains a table of performance requirements that apply to the schedule. Within the table, the requirements are organized into common requirements, which pertain to all protocols, protocol-specific requirements, and requirements that pertain to resource data being collected.
3. Expand the requirements tree, click the requirement to define, and define the requirement as follows:

Option	Description
Name	You can change the name of a performance requirement to improve readability. However, changing a requirement name causes a mismatch between the Performance Requirements report, which uses the changed name, and the other reports, which use the default name. Therefore, when you change a requirement name, be sure to keep track of the original name.
Operator	Select an operator.
Value	Type a value.
Standard	Click to make the requirement standard. If a standard requirement is not met, the schedule run will have a verdict of fail. Clear to make the requirement supplemental. In general, supplemental requirements are used for requirements that are tracked internally. A supplemental requirement cannot cause a run to fail, and supplemental results are restricted to two pages of the Performance Requirements report.

 

 

另外還有一些指令碼編輯功能的改進，例如Split Test（分割測試指令碼）、新增測試變數用於在測試指令碼間共享資料、在錄製指令碼過程中新增註釋、插入事務等，還可以在執行測試過程中檢視虛擬使用者，這個功能類似於LoadRunner中的Show browser during replay功能（Tools – General Options – Display – Show browser during replay）

 

 

關於RPT8.0的新特性可參考：

http://blog.csdn.net/Testing_is_believing/archive/2010/02/04/5287801.aspx