running
Differences
This shows you the differences between two versions of the page.
|
running [2020/05/11 12:53] montse |
running [2024/11/27 13:18] (current) montse [Test Set Window] |
||
|---|---|---|---|
| Line 43: | Line 43: | ||
| * Delete Test Set. | * Delete Test Set. | ||
| * Run Test Set. | * Run Test Set. | ||
| + | * Move Test Set. | ||
| ==== Test Set Window ==== | ==== Test Set Window ==== | ||
| - | {{:en:tsmanagement-testset_eng.png?2600|}}\\ \\ | + | {{ ::running3.png?direct&2600 |}}\\ \\ |
| It is accessed by clicking on any Test Set in the // Test Sets // window. | It is accessed by clicking on any Test Set in the // Test Sets // window. | ||
| In this window you can perform actions on the Test Sets, as well as manage the Test Case Data associated with the Test Set: | In this window you can perform actions on the Test Sets, as well as manage the Test Case Data associated with the Test Set: | ||
| Line 71: | Line 72: | ||
| * Delete Test Case Data. | * Delete Test Case Data. | ||
| - | {{:tsmanagement-addtcdata-eng.png?2600|}}\\ \\ | + | {{ ::running4.png?direct&2600 |}}\\ \\ |
| To include Test Case Data in the Test Set, press button "+" at the right of the Test Set name. A new window will open and will allow to select the Diagram, so that all available and selectable Test Case Data will be shown in the left-hand list. | To include Test Case Data in the Test Set, press button "+" at the right of the Test Set name. A new window will open and will allow to select the Diagram, so that all available and selectable Test Case Data will be shown in the left-hand list. | ||
| * Clicking over eachTest Case Data or "Select all" button will move the Test Case Data to the right-hand list. | * Clicking over eachTest Case Data or "Select all" button will move the Test Case Data to the right-hand list. | ||
| Line 118: | Line 119: | ||
| * **//Run to a higher step//**\\ \\ Again, we can advance to a higher step by entering the desired step in the **Step field**, and then pressing the **Run to next step** button.\\ \\ {{ :en:debuggs7.png?600 |}} \\ \\ Thus, the application will execute all the steps from the current one to the one immediately prior to this. From here we can continue the execution in the desired way. | * **//Run to a higher step//**\\ \\ Again, we can advance to a higher step by entering the desired step in the **Step field**, and then pressing the **Run to next step** button.\\ \\ {{ :en:debuggs7.png?600 |}} \\ \\ Thus, the application will execute all the steps from the current one to the one immediately prior to this. From here we can continue the execution in the desired way. | ||
| - | * **//Run to the last step of the TCV//**\\ \\ From any step, we will be able to advance directly to the end of the diagram, and there will be two ways to do this:\\ \\ a. By entering the last step of the diagram and pressing **Run to next step**. Remember: the execution will continue until the step immediately preceding the last step.\\ or \\ b. By pressing the **Start** button in the **Action column**. Then the application will run from the current step to the end of the diagram.\\ \\ {{ :en:debuggs8.png?600 |}}\\ \\ | + | * **//Run to the last step of the TCV//**\\ \\ From any step, we will be able to advance directly to the end of the diagram, and there will be two ways to do this:\\ \\ a. By entering the last step of the diagram and pressing **Run to next step**. Remember: the execution will continue until the step immediately preceding the last step.\\ or \\ b. By pressing the **Start** button in the **Action column**. Then the application will run from the current step to the end of the diagram.\\ \\ {{ :en:debuggs8.png?600 |}}\\ |
| 3. **Stopping the debug execution of a //TCV//** | 3. **Stopping the debug execution of a //TCV//** | ||
| Line 132: | Line 133: | ||
| However, if we wanted to go to a certain step inside a gate, then we would need to use points.\\ \\ | However, if we wanted to go to a certain step inside a gate, then we would need to use points.\\ \\ | ||
| For example, if we see (or type) this in the **step field**:\\ \\ {{ :en:debuggs10.png?600 |}}\\ It would mean that current step is (or if the user has typed it, he wants to advance to):\\ | For example, if we see (or type) this in the **step field**:\\ \\ {{ :en:debuggs10.png?600 |}}\\ It would mean that current step is (or if the user has typed it, he wants to advance to):\\ | ||
| - | Step 10 of the main diagram (in this example, step 10 would be a Gate, e.g. gate1),\\ | + | Step 10 of the main diagram (in this example, step 10 would be a Gate, e.g. gate1), and within gate1 to its step 5 (in this example step 5 of gate1 is another nested gate, e.g. gate2),and finally to the step 1 inside gate2.\\ \\ |
| - | and within gate1 to its step 5 (in this example step 5 of gate1 is another nested gate, e.g. gate2),\\ | + | |
| - | and finally to the step 1 inside gate2.\\ \\ | + | |
| Line 148: | Line 147: | ||
| {{ :en:debuggs13.png?600 |}}\\ \\ | {{ :en:debuggs13.png?600 |}}\\ \\ | ||
| Once the debug execution of a //TCV// has started, the **Results uploading** will be automatically disabled for obvious reasons. The user can enable it again when the debug execution ends, or when he wants to run the normal execution mode.\\ \\ | Once the debug execution of a //TCV// has started, the **Results uploading** will be automatically disabled for obvious reasons. The user can enable it again when the debug execution ends, or when he wants to run the normal execution mode.\\ \\ | ||
| - | {{ :en:debuggs14.png?600 |}}\\ \\ | + | {{ :en:debuggs14.png?600 |}}\\ |
| + | |||
| + | |||
| + | 6. **Console in Tast Client Debug Mode** | ||
| + | |||
| + | Once a debug execution has started with any diagram, you can open a console window to see the execution results in real time. | ||
| + | |||
| + | To do this, when you start a debug execution, you can press the log button at the right side, to open the console window for this execution.\\ | ||
| + | |||
| + | |||
| + | {{ :en:cdebug1.png?600 |}}\\ | ||
| + | |||
| + | |||
| + | Then a modeless window is shown, like below. As the diagram runs you can see the execution results on it. A scroll bar will appear when it will be necessary, and you can use even a small contextual menu (pressing right mouse button) for example to select or copy some content to pasteboard.\\ \\ | ||
| + | |||
| + | |||
| + | {{ :en:cdebug2.png?600 |}}\\ | ||
| + | |||
| + | It is also possible to show as many consoles as you need, one for each test run you are currently executing in debug mode. | ||
| + | |||
| + | Once the debug mode run stops, the console window automatically closes, returning the log button back to its usual behavior.\\ \\ | ||
| + | |||
| + | |||
| + | |||
| Line 171: | Line 194: | ||
| {{:Calendar_1.png??}}number of plannings requested. This is the initial status, when a planning is created \\ | {{:Calendar_1.png??}}number of plannings requested. This is the initial status, when a planning is created \\ | ||
| - | {{:Calendar_2.png?}} number of plannings confirmed. The planning is put //confirmed// when the user clicks the //Confirm// button that appears when editing the planned Test Set (tab [[en:running#plan_list|Plan List]])\\ | + | {{:Calendar_2.png?}} number of plannings confirmed. The planning is put //confirmed// when the user clicks the //Confirm// button that appears when editing the planned Test Set (tab [[running#plan_list|Plan List]])\\ |
| - | {{:Calendar_3.png?}} number of plannings rejected. The user has the option to reject the planning for different reasons (clicking the //Reject// button that appears when editing the planned Test Set (tab [[en:running#plan_list|Plan List]])\\ | + | {{:Calendar_3.png?}} number of plannings rejected. The user has the option to reject the planning for different reasons (clicking the //Reject// button that appears when editing the planned Test Set (tab [[running#plan_list|Plan List]])\\ |
| {{:Calendar_4.png?}} number of plannings executed. This status appears once the planning has been executed. | {{:Calendar_4.png?}} number of plannings executed. This status appears once the planning has been executed. | ||
| Line 181: | Line 204: | ||
| The steps to follow until the execution of the planned test cases are: | The steps to follow until the execution of the planned test cases are: | ||
| - | - Include the diagram (s) in a Test Set: through the TAST option [[en:running#test_set_management|TS Management]] | + | - Include the diagram (s) in a Test Set: through the TAST option [[running#test_set_management|TS Management]] |
| - Include the Test Set in a planning: through the New planification buttom of Planning | - Include the Test Set in a planning: through the New planification buttom of Planning | ||
| - Confirm the planning | - Confirm the planning | ||
| - | Once the Test Set has been executed, the result of the execution will be shown in the table of [[en:results|Results]]. | + | Once the Test Set has been executed, the result of the execution will be shown in the table of [[results|Results]]. |
| If the Test Set has not been executed, it will be canceled. | If the Test Set has not been executed, it will be canceled. | ||
| Line 191: | Line 214: | ||
| ^ Situation ^ Probable causes^ Corrective actions^ | ^ Situation ^ Probable causes^ Corrective actions^ | ||
| |The planned Test Set has not been executed|The server was not available|- Check the server is in the list\\ - Check the PC client is active in the server\\ - Check the Test Set is programmed for that server| | |The planned Test Set has not been executed|The server was not available|- Check the server is in the list\\ - Check the PC client is active in the server\\ - Check the Test Set is programmed for that server| | ||
| + | |||
running.1589201601.txt.gz · Last modified: 2020/05/11 12:53 by montse
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
