Difference between revisions of "GXtest Designer ユーザーズマニュアル"
(Created page with "{{Idiomas | Manual de Usuario de GXtest Designer 2.0 | GXtest Designer 2.0 User's Manual }} category:GXtest Guides category:GXtest Designer The objective of GXtest De...") |
(→Content) |
||
| Line 16: | Line 16: | ||
== Content == | == Content == | ||
| − | 1. [[GXtest Designer GUI]] | + | 1. [[GXtest Designer-GUI]] |
| − | 2. [[ | + | 2. [[ログイン / 接続]] |
| − | 3. [[GXtest | + | 3. [[GXtest プロジェクト]] |
| − | 4. [[GXtest | + | 4. [[GXtest および GeneXus KB]] |
| − | 5. [[ | + | 5. [[テストケース]] |
| − | 6. [[GXtest | + | 6. [[GXtest コマンド]] |
| − | 7. [[ | + | 7. [[データプールの使用]] |
| − | 8. [[ | + | 8. [[共有ワークスペース]] |
Revision as of 19:54, 6 November 2013
 |
 |
 link= {{{3}}} |
The objective of GXtest Designer is to easily model a Test Case and do the same for application made with GeneXus on different platforms and with different versions of GeneXus.
Test Cases are modeled on an as a diagram made up of a cluster of Nodes and Edge Lines, where the nodes represent the pages of an application and the edge lines represent the events that happen going from one Page to another. These elements (pages and events) can have commands associated with them. There are three types of commands: actions, validations and events. The three types are explained in more detail in the Commands section. In addition, you can include embedded Test Cases in a model to create modules that can be reused.
You can also include Decision nodes that choose which action to be taken depending on the result of a Validation. All of these concepts will be explained in more detail in the manual.
Content
2. ログイン / 接続
5. テストケース
6. GXtest コマンド
7. データプールの使用
8. 共有ワークスペース
