【正文】 emented in certain prepiled foundation libraries (., the MFC of Mic rosoft Visual C++, JDK of Java, and the VCL of C++ Builder). In this paper, we only study the code specially implemented for the AUT. The handlers in prepiled foundation libraries are not concerned. In brief, if an event is responded by the code in prepiled libraries, or is not responded by any code at all, we say that the event does not call any event handler. Dmax are defined based on the length of the shortest path between two events on the eventflow graphs (EFGs) and the integration tree (IT) [10] of the AUT (referring to [10] for the definition of EFG and IT). Note that when two events are contained in different EFGs, the shortest path between them is the shortest path on a global EFG whic h is the binatio n2 of all EFGs and the IT of the AUT. Let d(ei,ej) denote the le ngth of the shortest path between two events ei and ej. Given a test case t = ?S0, e1?！?。 en?, where event e1 can be accepted by the application in S0, and event ei can be accepted right after event ei1 is executed (for i = 2,3,…, n). Commonly, S0 can be any state in which the GUI object with respect to e1 is enable and visible. B. GUI Test Case Characteristics A GUI test case contains an event sequence. By analyzing the event sequence, we can get many characteristics of the test case. Table 1 shows some of them. Table 1 GUI Test Case Characteristics Characteristic Description L The length of a GUI test case NH The number of handler calls of a GUI test case PR The proportion of reachability events in a GUI test case Dmax The maximum length of the shortest path between two events in a GUI test case N(w) The number of times that a GUI test case operates on window w The length of a test case (denoted as L) is the le ngth of the event sequence contained in the test case. It is the “granularity” property of a GUI test case (the amount of input given by the test case, referring to [11]). L has been shown significantly affecting the fault detection in testing [11][12]. For example, the L of a GUI test case ?S0, e1。 Third International Conference on Software Testing, Verification, and Validation Workshops On Modeling of GUI Test Profile Lei Zhao and KaiYuan Cai$ Department of Automatic Control Beijing University of Aeronautics and Astronautics Beijing, China 100191 Abstract – GUI (Graphical User Interface) test cases contain much richer information than the test cases in nonGUI testing. Based on the information, the GUI test profiles can be represented in more forms. In this paper, we study the modeling of the test profiles in GUI testing. Several models of GUI test profiles are pro posed. Then we present a methodology of studying the relationship between the test profiles and the fault detection in GUI testing. A control scheme based on this relationship that may be able to improve the efficiency of GUI testing is also proposed. Keywords – GUI testing, test profile modeling, test case characteristics I. INTRODUCTION Due to the widespread usage of Graphical User Interfaces (GUIs) in various software applications/systems, GUI testing has attached much importance to software development. GUI testing means the testing of GUI applications, including the testing of GUIs’ function and structures, as well as the underlying code behind GUIs. GUI applications have many features different from nonGUI applications: the inputs to a GUI application are events。 一定數(shù)量的測試在執(zhí)行案例后，可以從歷史數(shù)據(jù)中得到一些知識，然后控制器在線調整測試配置，該控制器是基于測試剖面和故障檢測之間的關系，在圖 4 中，即 可獲得檢測的結果，她試圖以近似的測試配置文件，可以最大限度的提高 F（ λ； a1。這些測試用例執(zhí)行錯誤版本 AUT 上的 GUI 測試，故障尊重每個測試配置 TP（ λ）的平均數(shù)量。這種模式意味著可達性百分比概率 P是事件∫ △ /2△ /2fα ， β （ p） dp,通過調整 α 和 β 的值，我們可以改變測試配置文件的形式，如圖 3 所示。因此，測試配置文件可以看作泊松分布的 L： TP(λ) = {(L=k， λk1eλ/(k1)!,k=1,2,… .｝， （ 1） 其中（ k1） !是（ k1）的因素 上述的試驗剖面模 型，測試 k 時的長度的概率是 λ k1eλ /(k1)!,如圖 1 所示，λ是試驗剖面參數(shù)，這是一個非均勻的試驗剖面。在 GUI 測試中， GUI 測試情況下提供豐富的信息特點，比如說一些特點將在第二節(jié)中介紹。e2。e2… en 是 n。總之，如果一個預編譯的代碼庫事件做出了回應或者任何代碼都沒有被回應，我們就說事件沒有調用任何處理器程序。 二、 GUI 測試用例的特點 在這部分，首先我們將介紹 GUI 測試用例的定義，然后 GUI 測試案件的特點也將會被討論。每個這些方面的特性都代表了一種測試用例如何來測試應用程序的測試（ AUT）。 關鍵詞 — GUI 測試，測試剖面模型，測試用例特點 一、引言 由于圖形用戶界面在各種軟件應用程序 /系統(tǒng)中廣泛使用， GUI 測試重視軟件的開發(fā)?；谶@些摘要信息， GUI 測試資料可表現(xiàn)在更多的形式中。這些特點使 GUI 測試不同于非 GUI 應用程序測試。同樣的，在一個軟件應用程序的測試中，電路的故障檢測是受測試剖面的影響。通常，一個事件只能在特定的國家接受 GUI 應用程序進而進行檢測，例如，相應的 GUI 對象是可見的和具有啟用的狀態(tài)， GUI 應用程序的“狀態(tài)”是很重要的執(zhí)行事件。也就是說， 一個 GUI 測試案例可以表示為 S0的 e1。 PR是一個測試案例中的所有事件的比例可達事件，可達性【 12】的事件，在打開菜單或窗口（模特點 描述 L GUI測試案例的長度 NH 處理一個 GUI測試案例電話的次數(shù) PR 在 GUI測試案例中事件所占的比例 Dmax 在一個 GUI 測試案例中最大長度的兩個事 件之間的最短路徑 N（ w） 一個 GUI測試案例在 w窗口中的操作次數(shù) 態(tài)窗口或無窗【 10】）。 Dmax= max{d(ei,ej)} （ 1≦ i﹤ j≦ n） 這一特點，介紹了測試案例在 AUT 的 GUI 中可以達到的“深度 ”。 一個測試配置的基本形式是統(tǒng)一的試驗剖面模型，也就是說，不同的測試案例都使用同樣的概率。類似的概率分布（如 二項分布），也可以用作試驗剖面模型。 三、 GUI 測試配置文件和故障檢測 在上一節(jié)我們已經(jīng)介紹了八款 GUI 測試型材，在本節(jié)中，我們首先介紹如何研究試驗剖面和故障檢測之間的關系，然后，控制計劃提出了改進 GUI 測試的測試效率。本文在試驗剖面模型的基礎上，我們將提出一個網(wǎng)上直銷的方式，來調整測試配置文件。這意味著控制器在嘗試更多的故障檢測與給定的測試用例數(shù)。e2。 en? is n. The number of event handler calls, denoted as NH, is the times of the test case calling event handlers. This characteristic neglects the events that do not call any event handler in the source code. Obviously, NH ? L. PR is the proportion of reachability events to all events in a This characteristic describes how “deep” a test case can reach in the GUIs of the AUT. The GUIs