modeling
Differences
This shows you the differences between two versions of the page.
|
modeling [2021/09/30 14:31] ana [Selective Mapping] |
modeling [2024/02/19 10:01] (current) montse [Information about the management of UML diagrams] |
||
|---|---|---|---|
| Line 314: | Line 314: | ||
| We can see the diagram information by clicking on the 'More info' icon.\\ You can page the diagrams using the page numbers at the bottom of the screen.\\ \\ This screen allows: | We can see the diagram information by clicking on the 'More info' icon.\\ You can page the diagrams using the page numbers at the bottom of the screen.\\ \\ This screen allows: | ||
| - | - [[en: New_diagram: Create a new diagram (// New diagram // option)]].\\ | + | - [[:New_diagram: Create a new diagram (// New diagram // option)]].\\ |
| - | - [[en: Import XMI: Import a XMI file from a directory (// Import XMI // option)]].\\ | + | - [[:Save a diagram: Save the information of the active diagram on screen (diskette icon)]].\\ |
| - | - [[en: Save a diagram: Save the information of the active diagram on screen (diskette icon)]].\\ | + | - [[:Delete diagram: Delete a diagram, using the bin icon]].\\ |
| - | - [[en: Delete diagram: Delete a diagram, using the bin icon]].\\ | + | - [[:Create New Folder: Create a new folder (// + Folder // option)]].\\ |
| - | - [[en: Create New Folder: Create a new folder (// + Folder // option)]].\\ | + | - [[:Filter diagrams: Select diagrams using user filters and mappings, clicking the filter icon]].\\ |
| - | - [[en: Filter diagrams: Select diagrams using user filters and mappings, clicking the filter icon]].\\ | + | - [[:Delete filters: Deactivate the filters used, using the cross icon]].\\ |
| - | - [[en: Delete filters: Deactivate the filters used, using the cross icon]].\\ | + | - [[:Edit diagram: Edit a diagram for its update, double click ]].\\ |
| - | - [[en: Edit diagram: Edit a diagram for its update, double click ]].\\ | + | |
| ===== Message Properties Tab ===== | ===== Message Properties Tab ===== | ||
| Line 386: | Line 385: | ||
| - | {{:move1.png?nolink&700|}} | + | {{:move1.png?link&700|}} |
| - | {{:move2.png?nolink&700|}} | + | {{:move2.png?link&700|}} |
| ===== Global Variables ===== | ===== Global Variables ===== | ||
| Line 399: | Line 398: | ||
| {{:Global Variables_eng_1.png?nolink&1800|}} | {{:Global Variables_eng_1.png?nolink&1800|}} | ||
| - | In TAST, there are currently three global variables: | + | In TAST, there are currently these global variables: |
| - | * **#stepResult:** boolean variable that contains the result of the last step execution in the test case: | ||
| - | * true: when the result of the last step execution has been correct. | ||
| - | * false: otherwise; that is, the result of the last step execution has been failed. | ||
| * **#caseResult:** boolean variable that contains the result of the test case execution: | * **#caseResult:** boolean variable that contains the result of the test case execution: | ||
| * true: when the result of all steps execution of the test case has been correct. | * true: when the result of all steps execution of the test case has been correct. | ||
| * false: otherwise; that is, at least the execution of a step of the test case has been failed. | * false: otherwise; that is, at least the execution of a step of the test case has been failed. | ||
| + | * **#global_password:** Contains the client access password. | ||
| + | * **#global_user:** Contains the client access user | ||
| * **#pathLog:** contains the path to the folder, which contains the screenshots, log file and other files generated during the execution. | * **#pathLog:** contains the path to the folder, which contains the screenshots, log file and other files generated during the execution. | ||
| + | * **#stepNumber:** It contains a four-character number (e.g. '0001') and represents the number by which the next step marked to be documented in ALM will be recorded. When a step is recorded in ALM, this number will be incremented for the next step. | ||
| + | * **#stepNumberTast:** Contains the old numbering for documenting steps in ALM before the 'stepNumber' variable was available. This format is "Step X.Y...Z Loop I.J...K" where X...Z is the step position, where Y...Z are positions within Gates, and I...K are the loop iteration number, where J...K are the iteration number of nested loops. | ||
| + | * **#stepResult:** boolean variable that contains the result of the last step execution in the test case: | ||
| + | * true: when the result of the last step execution has been correct. | ||
| + | * false: otherwise; that is, the result of the last step execution has been failed.\\ \\ | ||
| + | |||
| ===== Predefined Functions - Generation of evidences ===== | ===== Predefined Functions - Generation of evidences ===== | ||
| Line 581: | Line 586: | ||
| |setBearerTokenAuthentication|API/WebService| NO | | |setBearerTokenAuthentication|API/WebService| NO | | ||
| |setDigestAuthentication|API/WebService| NO | | |setDigestAuthentication|API/WebService| NO | | ||
| - | |containsText|Host 3270| NO | | + | |clearAndWriteField|Host 3270| YES | |
| + | |clearField|Host 3270| YES | | ||
| + | |containsText|Host 3270| YES | | ||
| + | |getLenghField|Host 3270| NO | | ||
| |nextScreen|Host 3270| YES | | |nextScreen|Host 3270| YES | | ||
| |previousScreen|Host 3270| YES | | |previousScreen|Host 3270| YES | | ||
| - | |readField|Host 3270| NO | | + | |readField|Host 3270| YES | |
| |readRow|Host 3270| YES | | |readRow|Host 3270| YES | | ||
| |readScreen|Host 3270| YES | | |readScreen|Host 3270| YES | | ||
| - | |rowContainsText|Host 3270| NO | | + | |readScreen|Host 3270| YES | |
| + | |rowContainsText|Host 3270| YES | | ||
| |waitCRC|Host 3270| NO | | |waitCRC|Host 3270| NO | | ||
| + | |waitFor|Host 3270| NO | | ||
| |waitForChange|Host 3270| YES | | |waitForChange|Host 3270| YES | | ||
| |waitForText|Host 3270| YES | | |waitForText|Host 3270| YES | | ||
| - | |writeAfterLabel|Host 3270| NO | | + | |writeAfterLabel|Host 3270| YES | |
| - | |writeBeforeLabel|Host 3270| NO | | + | |writeBeforeLabel|Host 3270| YES | |
| - | |writeField|Host 3270| NO | | + | |writeField|Host 3270| YES | |
| |writeKey|Host 3270| YES | | |writeKey|Host 3270| YES | | ||
| + | |writeKeyUntilFind|Host 3270| YES | | ||
| |writeText|Host 3270| YES | | |writeText|Host 3270| YES | | ||
| |checkTextInSlide|PDF| NO | | |checkTextInSlide|PDF| NO | | ||
| Line 636: | Line 647: | ||
| ===== Shortcuts ===== | ===== Shortcuts ===== | ||
| - | To speed up the Modeling phase, TAST offers a set of shortcuts: | + | |
| + | You can use the following keyboard shortcuts in the canvas: | ||
| ^ Shortcut ^Description^ | ^ Shortcut ^Description^ | ||
| - | |ESC | Close menus and selects pointer| | + | |ESC | Close menus and selects the pointer.| |
| - | |ctrl+shift+c| Copy messages| | + | |Alt + 9 | DUnlocks diagrama for editing.| |
| - | |ctrl+shift+f| Comment in/out message or gate| | + | |Alt + P | Selects the pointer tool.| |
| - | |ctrl+shift+v| Paste messages| | + | |Alt + O | Selects the "Object" tool.| |
| - | |L| Select list of messages| | + | |Alt + M | Selects the "Message" tool.| |
| - | |M| Select multiple messages| | + | |Alt + R | Selects the "Reply message tool".| |
| - | |Alt+M| Select Message| | + | |Alt + G | Selects the "Gate" tool.| |
| - | |Alt+R| Select Reply message| | + | |Alt + A | Selects the "Combined Fragment: ALT" tool.| |
| - | |Alt+P| Select Pointer| | + | |Alt + D | Selects the "Combined Fragment: DO WHILE" tool.| |
| - | |Alt+O| Select Object| | + | |Alt + W | Selects the "Combined Fragment: WHILE" tool.| |
| - | |Alt+G| Select Gate| | + | |Alt + F | Selects the "Combined Fragment: FOR" tool.| |
| - | |Alt+Y| Select Combined Fragment| | + | |Alt + E | Selects the "Combined Fragment: FOR EACH" tool.| |
| - | |Z+Plus| Zoom in| | + | |Alt + S | Selects the "Subtestcase" tool.| |
| - | |Z+Minus| Zoom out| | + | |Ctrl + C| Copy selected elements.| |
| - | |Supr| Delete element (only applies if there is an element selected in the diagram)| | + | |Ctrl + V| Paste copied elements.| |
| - | |Alt+0| Select the "Move Diagram" tool| | + | |Ctrl + Z| Undoes some actions such as: Delete elements, Redistribute diagram, etc...| |
| + | |Double click | Edit element: double click on a diagram element to edit its properties.| | ||
| + | |Right button | Context menu: by right-clicking on an element, you can access the dynamic context menu. The options of this menu vary and can appear active/not active, depending on the currently selected elements.| | ||
| + | |Mouse Wheel | Zoom in/Zoom out: Roll the mouse wheel forward or backward to zoom in or zoom out the canvas respectively.| | ||
| + | |Shift + click| Multiple selection: hold down the shift key and click on different elements to select them.| | ||
| + | |Shift + drag | Multiple scrolling: hold down the shift key while scrolling the selected elements.| | ||
| + | |Click + drag | Move diagram: click on an empty area of the diagram while dragging in any direction to move the diagram.| | ||
| + | \\ \\ | ||
| Line 721: | Line 741: | ||
| The configuration, how to use the functionality, and some considerations are explained in the document below: | The configuration, how to use the functionality, and some considerations are explained in the document below: | ||
| - | {{:TAST Selective Mapping_v0.4.2_.doc|tast_selective_mapping_v0.4.2.doc}} | + | {{:TAST Selective Mapping_v1.0.doc|tast_selective_mapping_v1.0.doc}} |
| ===== Tast Table Data Management ===== | ===== Tast Table Data Management ===== | ||
| - | In an UML diagram, TAST allows the use of variables of a specific type of table, called **TASTTABLEDATA**.\\ \\ These variables can be used with practically all the adaptors available in TAST (HTML GUI, Excel Files, Database, …). They can be used in the "Value" box of a Predefined Function or in Javascript.\\ \\ Once the TASTTABLEDATA variables have been created (as output variables), they can be used as input variables in subsequent messages. The way to use them in a "Value box" is:\\ #TasTableDataVariableName.functionName(params…). | + | In an UML diagram, TAST allows the use of variables of a specific type of table, called **TASTTABLEDATA**.\\ \\ These variables can be used with practically all the adaptors available in TAST (HTML GUI, Excel Files, Database, …). They can be used in the "Value" box of a Predefined Function or in Javascript.\\ \\ Once the TASTTABLEDATA variables have been created (as output variables), they can be used as input variables in subsequent messages. The way to use them in a "Value box" is:\\ #TastTableDataVariableName.functionName(params…). |
| From javascript, you will use the syntax functionName(params…)\\ \\ The functions currently available are: | From javascript, you will use the syntax functionName(params…)\\ \\ The functions currently available are: | ||
| Line 748: | Line 768: | ||
| {{ :tasttabledata_4_eng.png?nolink |}} | {{ :tasttabledata_4_eng.png?nolink |}} | ||
| - | ===== TAST Row Data Management===== | + | ===== Tast Row Data Management===== |
| - | TAST allows the use of variables of a specific type of row, called **TASTROWVALUES**.\\ \\ These variables can be used with practically all the adaptors available in TAST (HTML GUI, Excel Files, Database, …). They can be used in the "Value" box of a Predefined Function or in Javascript.\\ \\ Once the TASTROWVALUES variables have been created (as output variables), they can be used as input variables in subsequent messages.\\ \\ The way to use them in a "Value box" is: #TasRowDataVariableName.functionName(params…) | + | TAST allows the use of variables of a specific type of row, called **TASTROWVALUES**.\\ \\ These variables can be used with practically all the adaptors available in TAST (HTML GUI, Excel Files, Database, …). They can be used in the "Value" box of a Predefined Function or in Javascript.\\ \\ Once the TASTROWVALUES variables have been created (as output variables), they can be used as input variables in subsequent messages.\\ \\ The way to use them in a "Value box" is: #TastRowDataVariableName.functionName(params…) |
| From javascript, you will use the syntax functionName(params…)\\ \\ The functions currently available are:\\ | From javascript, you will use the syntax functionName(params…)\\ \\ The functions currently available are:\\ | ||
| Line 1001: | Line 1021: | ||
| * **Keys:** They are every word that comes before “ : ”\\ | * **Keys:** They are every word that comes before “ : ”\\ | ||
| * **Value:** Value is what comes after “ : ”\\ | * **Value:** Value is what comes after “ : ”\\ | ||
| - | * **Properties:** Is the entire path that includes the keys until the “ : ” using “ _ ” to separate them.\\ | + | * **Properties:** Is the entire path that includes the keys until the “ : ” using “ _ ” to separate them.\\ \\ Example:{{ :en:xpath1en.png?600 |}}\\ Also, you can do subkeys:{{ :en:xpath2en.png?600 |}}\\ So in the end, the variable will have all the properties separated by “_” in this example should be: #wiki_url1.\\ \\ The first key will always be one of the following words:{{ :en:repo11esp.png?200 |}} |
| - | Example:{{ :en:xpath1en.png?600 |}} | + | |
| - | + | ||
| - | Also, you can do subkeys:{{ :en:xpath2en.png?600 |}} | + | |
| - | So in the end, the variable will have all the properties separated by “_” in this example should be: #wiki_url1.\\ | + | |
| - | + | ||
| - | The first key will always be one of the following words: | + | |
| - | + | ||
| - | {{ :en:repo11esp.png?200 |}} | + | |
| Line 1021: | Line 1033: | ||
| * Clone a repository already imported into a new one. | * Clone a repository already imported into a new one. | ||
| * Watch information about repositories such as creation date and diagrams that use it, works like more information tab in modeling. | * Watch information about repositories such as creation date and diagrams that use it, works like more information tab in modeling. | ||
| - | * Locate where a repository is being used. | + | * Locate where a repository is being used.\\ \\ |
modeling.1633012317.txt.gz · Last modified: 2021/09/30 14:31 by ana
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
