Parameter files.

Parameter files

We can use parameters to provide values that a test case should use as it executes.
At runtime, that test case can use parameter values from serveral sources: testbeds, session profiles, and the parameters that you configured on test test case uses the parameters defined parameter definitions in the referenced files are included.

You can define parameters and their values in several places in Spirent iTest. One powerful way to cause Spirent iTest to use a particular set of parameter definitions when executing any test case is to create a parameter file.

Advanced merging behavior for parameters

Parameter files are often used to parameterize the overall operation of a test case. A parameter file is a collection of parameter definitions. In addition, a parameter file can include one or more other parameter files (the parameter definitions in the included files are added to the local definitions). Parameter files contain XML with virtually any schema and use the .ffpt filename extension.

Global parameter file

You can specify that a particular parameter file is the Global parameter file. The only parameter file that is automatically used by test cases is the Global parameter file. The Global parameter file applies to all test cases in a workspace.

Important There is no way to specify a particular parameter file for a test case. You can, however, use iTestRT or itestcli to specify a particular parameter file (that is, not the Global parameter file) for use by a particular test case.

Value:

Multiple values for a single parameter are useful, for example, in foreach loops. To create a parameter with multiple values, do either of the following:

How to ignore the model number of Window.

issue number of Fanfare: SR 1-317728520

if the browser will assign the number to windows, and the number is diffident each times.

we should use query currectWindos() to get the number and store it to a variable.
after that use selectWindow to select the window.

Integrate IxChariot and iTest by TCL

All the IxChariot TCL and C sample script save in 

        C:\Program Files\Ixia\IxChariot\SDK\samples\


save the result by time:


#set testFile "chrpairstest.tst"
set systemTime [clock seconds]
set testFile "../../../[clock format $systemTime -format %Y%m%d-%H%M%S].tst"

QuickCall

QuickCall is used only during session.
if you want to use it in the every test case, you need to global it.

Chapter 30 - The iTest Builder

Building projects:
The builder process ensures that all files and resources that depend on each other are properly linked so that updates to one resource are reflected in all of its dependent resources. this ensures that tests will execute correctly. The builder detects dependency problems and either fixes them or displays Warnings or Errors in the problems view.

該Builder 過程確保所有文件和資源，根據適當的linked，以便正確地更新一個資源都反映在其所有相關的資源。這個測試將確保正確執行。該builder檢測到的dependency問題，要嘛修復它們或顯示警告或錯誤的問題的看法。



When you delete a project, all other projects in the workspace are rebuilt to add error markers to the projects that reference the deleted project. if you then create a new project with the same name as the deleted project, iTest does not perform another build (for performance reasons) and the error markers in the projects remain (incorrectly).


To avoid this possible problem, when you add a new project or delete a project, perform a clean build (click project > clean > all ) 


當你刪除一個項目，其他所有項目都在workspace重建添加錯誤標記的項目，參照已刪除項目。如果你再創建一個新的項目具有相同的名稱為被刪除的項目，ITEST不執行另一個版本（由於性能原因）和錯誤標記的項目仍然（不正確）。

為了避免這種可能出現的問題，當你添加一個新的項目或刪除項目，執行清理生成 (click project > clean > all )

Command Break Characters

Specify the character code that the device interprets as a break (so you can manually cancel an executing step).
指定的字符代碼，該裝置解釋為中斷（所以你可以手動取消一個執行步驟）

Default: Ctrl-C 

To add the encoding for a character set like Ctrl-Z, click Record and then press the keys. iTest places the character code into the text box. Click Add to add the code to the set of command completion characters.
要添加一個編碼字符集類似於 CTRL- Z，點擊Record然後按該鍵。iTest地方的字符代碼到文本框中。點擊"Add"來加代碼到命令完成字符集。

Limitations of the Record feature:
• For the Alt key, iTest captures only the last key pressed. For example, Alt+q is recorded as “q”.
• Function keys are not recorded.

iTest with Spirent Test Centre_GUI

There is no option in STC-GUI to load the config file in run time.
But they can saves the config file from STC_GUI in iTest.

Topology, testbed, and device abtraction.

Feature categories for maintaining tests:

• Topology, testbed, and device abstraction

Maintain tests
Topology, testbed, and device abstraction
Graphical Topology Editor	Create and edit graphical topologies within iTest using new industry standard TBML files. Leverage a topology to start sessions and communicate iTest setup requirements with others. Device properties are conveniently aggregated and editable in properties view. Test reports include image snapshot of topology diagram.
Testbed definitions	Define testbeds as a set of named devices in separate testbed documents, so that test cases can port easily between different testbeds-even when the testbeds contain different versions or variants of the devices.  定義測試平台作為一套名為試驗台設備在單獨的文件，使testcase可以很容易在不同的測試平台端口，即使在測試平台包含了不同的版本或變種的設備。
Session profiles	Allow sessions to be started instantly and dragged and dropped into any test case. When devices or their properties change, the powerful abstraction techniques provided by iTest allow users to modify only the one session profile, rather than every test case
Scriptless parsing	Automatically convert raw text, unstructured data, and structured data (IP addresses, MAC addresses, timestamps, integers, real numbers, and so on) into easily manageable variables (tokens).
Scriptless analysis definitions	Declare expected behavior easily by selecting among a set of rules and arguments that are customized to the specific context, and then editing and/or combining the rules to achieve precisely the desired analysis.
Web page mapping	Convert a Web page into a set of easily recognized targets (links, buttons, text fields, tables) for easy test case maintenance and abstraction. When targets change on the page, users need to modify only the one map, rather than every test case.
Named variables, queries, and parameters	Specify and name critical variables/tokens (words, whitespace, numbers, IP addresses, timestamps) to enable test case portability across product variants.
Automatic Response Mapping (ARM)	ARM makes the generation of response maps easier by leveraging the gray boxes created with IRP to quickly create response maps. Query-based analysis rules constructed with IRP can be abstracted with the creation of a corresponding response map.
Response Map Wizard	Accelerates response map creation for a broad class of responses. When responses change, users need to modify only the one map, rather than every test case. This allows tests to be easily maintained for fully automated regression testing across releases.

iTestHow iTest Works

iTest® provides the necessary capabilities and multi-protocol support to accomplish simple feature testing, as well as sophisticated system and scenario testing. Following is an overview of how iTest works to build tests, create reports, add analysis, include powerful logic, as well as make tests portable and maintainable for "lights out" regression testing.


iTest orchestrates sophisticated system and scenario testing, configuring and managing hundreds of devices simultaneously while providing interactive testing with DUTs.



Queries can be defined in a response map or in local analysis rules.
In addition, iTest auto-generates queries for structured responses like Web, SNMP, Traffic generator devices, and XML

Queries 可以被定義為response map 或在local分析規則。
此外，iTest 自動產生Queries 為了結構化的responses ，如Web，SNMP和交通發電機設備和XML

Is the license key affected if we change the IP address or other?

Is the license key affected if we change the license server IP address, or any other information of the license server? Any change to the machine's network configuration will change the output of the ffhostid. Changes include (but are not limited to):

* Adding, removing a network card
* Enabling, disabling wireless feature
* Change in the IP address of the machine
* Change in the domain to which the machine is connected
* Being connected to one or more VPN accounts
* Having virtual network adapters installed (e.g. Hamachi)

iTest 4.1 新版上市！

面對即將來臨的 2011 年，我們很高興宣布 iTest 4.1 新版上市！

iTest 4.1增加了許多新功能和模組，這些新增功能將大幅精進用戶們在測試時，相關 testbed 與自動化的範疇！加上新推出的 Fanfare iCentral 產品的結合，更讓用戶原有的測試數據報表得以提升到更高的層次。以下分別針對 iTest 4.1 與 iCentral 1.0 主要新功能作綱要介紹：

iTest 4.1 Highlights:

Web Services module：
現在透過 SOAP 或 RESTful 等 Web 服務，用戶可經由應用程式的 API 來對企業用軟體 (EMS, OSS/BSS 等) 直接進行測試與自動化。

VNC module：
這是全新的模組，讓用戶可以針對各種作業系統進行視窗化控制 (OS-related controls)，Windows, Mac, 或 Linux 等均可支援。透過此項功能，用戶可將案例範疇大幅度擴展，可進行更複雜的測試，譬如 triple play testing, VOIP testing, VPN connection tests 等。

VMware vSphere module：
強大的 VMware 也可納入到自動化測試內了，透過這個新推出的模組，用戶可以整合 VMware 到案例內，不論是 Create, retrieve, update, delete, start, stop 等動作都可操作，是相當便利的模組！

Test Report Diff feature：
提供快速比對測試案例的異同，可雙邊顯示，方便用戶找出差異處做進階處理。

Plus... 更多更多的模組強化功能也都放在新版本 4.1 內，舉凡 Java Swing, Virtual Testbed (VTB), iTestRT, reporting enhancements... 您還在等什麼呢？

Fanfare iCentral Highlights:

兼容 iTest 4.1：
iCentral 可轉換既有的 iTest 測試結果到您的決策工具內，提供最佳資訊給測試與管理高層。

Web-based 儀表版：
版本 1.0 含括 web-based 儀表版功能，可協助用戶整合並組織其測試數據，藉以分析得知產品測試後的涵蓋率、測試分組項目的現況，以協助研判產品發行是否就緒。

用戶更新訊息

•合法用戶請立即下載最新的 iTest 4.1：所有合法的用戶均可以從廣聯科技取得最新的版本與說明文件！

•尚未購買軟體更新執照的用戶：您還在使用舊版的 iTest 嗎? 該更新您手邊的版本囉，立即享受新版本的強大與便捷！

•線上教學： 歡迎任何想瞭解 Fanfare 軟體功能的朋友們，透過 Fanfare 論壇所提供的線上教學站台獲取您想知悉的一切，請連上 Fanfare Learning Center (也可經由 iTest HELP 功能連上本網站).

•iTest Lite 試用版：還沒購買的客戶想親身感受 iTest 的魅力嗎? 歡迎到 iTest Lite 申請試用!

關於 Fanfare