This shows you the differences between two versions of the page.
en:running [2020/01/15 16:14] montse [Test Sets Window] |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Running ====== | ||
- | |||
- | This option of the TAST tool allows the user ** to execute the Test Sets. ** | ||
- | Also, it allows ** to create new Test Sets to be executed. ** | ||
- | |||
- | The RUNNING option has two tabs:\\ | ||
- | * Test Set Management | ||
- | * Planning | ||
- | |||
- | ===== Test Set Management ===== | ||
- | |||
- | With this option the Test Sets corresponding to a specific diagram can be managed. | ||
- | Here in Test Set Management are two different “tabs”: | ||
- | * Test Sets. | ||
- | * Test Set. | ||
- | |||
- | ==== Test Sets Window ==== | ||
- | {{:en:tsmanagement-testsets_eng.png?2600|}}\\ \\ | ||
- | It shows the list of Test Sets of a specific domain and project, with information about its status, as well as its Test Case Datasets. | ||
- | In general, it can be filtered by: | ||
- | * Domain. | ||
- | * Project. | ||
- | * Test set. | ||
- | * User. | ||
- | |||
- | It will also allow creating, editing and deleting a folder. | ||
- | |||
- | In the main window of MANAGEMENT OF TEST SETS, the list of Test Case Sets for the filters used will be displayed, with the following information:\\ | ||
- | * Name of the Test Set. | ||
- | * Date and time of creation. | ||
- | * Number of diagrams. | ||
- | * Number of data sets of test cases (TCD). | ||
- | * Status: The status shows the state of the Test Set execution, it also includes a global status, being aware of the individual status of every Test Case Data on the Test Set. That means we have different status: | ||
- | * Pending: Message **“not executed”** in a gray color. This status mean that never has existed an execution of that Test Set. | ||
- | * Executing: This status is not visible, it happens when the user executes the Test Set. | ||
- | * Partially Executed: The message in orange **“Partially Executed”** comes with a Test Set with various TCD when some of then were executed and the other ones don’t. | ||
- | * Completed: in this status we could get two messages: | ||
- | - **Executed (in green):** This means that all the execution went right, and everything finished without problems. | ||
- | - **Executed (in red):** This means that a problem has occurred in the Test Set or TCD.\\ | ||
- | The only way to get the status Executed in green, is when all the TCD are in green too. If something failed, then it will be red.\\ | ||
- | * Uploaded to ALM: YES or NO. | ||
- | * Action: with the following indicators: | ||
- | * Owner. | ||
- | * Delete Test Set. | ||
- | * Run Test Set. | ||
- | |||
- | ==== Test Set Window ==== | ||
- | {{:en:tsmanagement-testset_eng.png?2600|}}\\ \\ | ||
- | 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: | ||
- | * At the Test Set level: | ||
- | * Create a Test Set. | ||
- | * Run a Test Set. | ||
- | * Upload the Test Set to ALM: all steps of the set of test cases will be added to the tool [[https://en.wikipedia.org/wiki/HP_Application_Lifecycle_Management|ALM (Application Lifecycle Management).]] | ||
- | * At the Test Case Data level: | ||
- | * Add a Test Case Data. | ||
- | * Delete a Test Case Data. | ||
- | * Select / unselect the screenshots of the Test Case Data (of some Test Case Data or of all). | ||
- | |||
- | The list of all the Test Case Data corresponding to the Test Set on which it has been previously clicked will be displayed, with the following information: | ||
- | * Order. | ||
- | * Domain. | ||
- | * Project. | ||
- | * Folder. | ||
- | * Name of the diagram. | ||
- | * Type of Test Case Data (validation or value). | ||
- | * Result: Executed or Not executed. | ||
- | * Uploaded or not to ALM. | ||
- | * Action: with the following indicators: | ||
- | * Capture of the screenshots of the test case. | ||
- | * Scroll up or down the Test Case Data. | ||
- | * Delete Test Case Data. | ||
- | |||
- | {{:tsmanagement-addtcdata-eng.png?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. | ||
- | * Clicking over eachTest Case Data or "Select all" button will move the Test Case Data to the right-hand list. | ||
- | * The Test Case Data on the right-hand listwill show a "check/minus" button to show if the capture of evidences is active for that Test Case Data. We can alter the status by clicking on that button. There is a general button on top of the list to alter the status of all the elements at once. | ||
- | * Clicking on any Test Case Data on the right we will move it to the left if it belongs to the selected diagram, or will dissapear if it doesn´t. | ||
- | * All Test Case Data on the right-hand list will be loaded to the Test Set once we click over the "Accept" button of the screen. | ||
- | ===== Debug Mode Execution in client for TC_Validation ===== | ||
- | |||
- | To facilitate the execution of validation test cases, in TAST there is the possibility of executing them in debug mode (from the [[en:first_steps_in_tast#html_client|client]]). | ||
- | |||
- | This means that the user can choose if the execution is going to be done until a specific step, and then to decide whether to continue the execution of all the steps until the end of the test case, or if it is executed step by step. | ||
- | |||
- | Once logged in the [[en:first_steps_in_tast#html_client|TAST client]], a window similar to the following will open: | ||
- | |||
- | {{:Client_debug_eng_1.png?nolink&600|}} | ||
- | |||
- | As an example, we will start with the validation test case 'tcv__Adaptador-GUI_HTML_Simple', which consists of 6 steps: | ||
- | |||
- | {{:Client_debug_eng_3.png?nolink&400|}} | ||
- | |||
- | a) If you want the complete execution of the test case, you will click on the green 'play' button: | ||
- | |||
- | {{:Client_debug_eng_2.png?nolink&600|}} | ||
- | |||
- | And once executed the 6 steps, the [[en:first_steps_in_tast#html_client|client]] will display the result of execution: | ||
- | |||
- | {{:Client_debug_eng_4.png?nolink&600|}} | ||
- | |||
- | b) If you want the execution till a specific step (not inclusive) (eg, the number 5): | ||
- | * enter the step number till the execution must be stopped in the field 'Step' | ||
- | * click on the green 'play' button: | ||
- | |||
- | {{:Client_debug_eng_5.png?nolink&600|}} | ||
- | |||
- | And, as in case a), once the execution of the steps has been completed, the [[en:first_steps_in_tast#html_client|client]] will show the result of the execution, appearing in the column 'Status' the last step executed: | ||
- | |||
- | {{:Client_debug_eng_6.png?nolink&600|}} | ||
- | |||
- | c) If you want the execution of the test case till a specific step (not inclusive) (eg, number 5), and from there step by step until the end: | ||
- | * enter the step number till the execution must be stopped in the field 'Step' | ||
- | * click on the green 'play' button | ||
- | * click on the Debug green button, and the step will increase by 1 in 1: | ||
- | |||
- | {{:Client_debug_eng_5.png?nolink&600|}} | ||
- | |||
- | {{:Client_debug_eng_7.png?nolink&600|}} | ||
- | |||
- | {{:Client_debug_eng_6.png?nolink&600|}} | ||
- | |||
- | ===== Planning ===== | ||
- | |||
- | In TAST it is possible to schedule the Test Sets to be executed later. | ||
- | These plannings can be periodic. | ||
- | |||
- | The PLANNING option has two tabs: | ||
- | |||
- | * Calendar | ||
- | * Plan List | ||
- | |||
- | ==== Calendar ==== | ||
- | |||
- | In this Running option, you can see a calendar with the status of the existing plans for a Domain, Project, and, optionally, for a Specific Server: | ||
- | |||
- | {{:Calendar.png??nolink&9000}} | ||
- | |||
- | Below the meaning of the colored circles that appear in calendar days: | ||
- | |||
- | {{: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_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_4.png?}} number of plannings executed. This status appears once the planning has been executed. | ||
- | |||
- | ==== Plan List ==== | ||
- | |||
- | ==== Flow in the Test Cases Planning ==== | ||
- | |||
- | 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 Test Set in a planning: through the New planification buttom of 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]]. | ||
- | |||
- | If the Test Set has not been executed, it will be canceled. | ||
- | |||
- | ^ 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| |