Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • contact • BigCommerce WebService Access • Save a Bizweaver Workflow • Introduction (Import/Export) • Introduction (Test) • about
bw2:test_run_tool

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
bw2:test_run_tool [2020/12/15 14:19]
akoehler created 		bw2:test_run_tool [2021/07/19 16:26] (current)
akoehler Updated for 2.7
Line 1: Line 1:
-======Introduction (Test Run Tool)======+======Introduction (Test)======
  
 **Important Note** **Important Note**
  
 <WRAP center round alert> <WRAP center round alert>
-The Test Run tool does not use “dummy” transactions. This means that if you are doing data updates (e.g. via SQL or SAP Business One connector), the data is really updated. Do all testing against test data whenever possible to avoid issues with duplicated or incorrect data.+The test does not use “dummy” transactions. This means that the data is really updated if you are doing data updates (e.g., via SQL or SAP Business One connector). Do all testing against test data whenever possible to avoid issues with duplicated or incorrect data.
 </WRAP> </WRAP>
  
 =====General Operation===== =====General Operation=====
-To execute a workflow using the Test Run tool, open the workflow so that is displayed in the design canvas. Click the Test Run icon {{:bw:introimage15.png?30|}} in the toolbar to initiate processing.+To test a workflow, open the workflow design window. Click any of the test icons {{:bw2:bizweavernewtestrun0.png|}} in the toolbar to initiate processing.
  
-A new window is displayed at the bottom of the canvas area. This window contains functions to manage the execution cycle, view the workflow steps as they execute, and view variables as they become available.+A new window is displayed at the bottom of the design canvas. A tester can view the workflow steps in this window as they execute and view variables as they become available. All execution options are in the workflow design canvas toolbar. 
  
-{{  :bw:intromage16.png  |}}+{{ :bw2:bizweavernewtestrun1.png |}} 
 +{{ :bw2:bizweavernewtestrun2.png |}}
  
-  - Execute the current step. +  - Automatically step through the workflow at speeds 1,2,3. 
-  - Automatically step through the workflow.+    - Speed 1 executes a step every 2 seconds 
 +    - Speed 2 executes a step every second 
 +    - Speed 3 executes a step every .25 seconds  
 +  - Execute a single step.
   - Pause automatic execution.   - Pause automatic execution.
-  - Click the + or – buttons, or use the slider, to control the speed of automatic execution. +  - Stop testing
-  - Examine variable values (described below).+
   - Display area showing the current step, steps that have been executed, any variable values viewed, and any error messages that may occur. This information is also displayed in the block at the bottom of the canvas.   - Display area showing the current step, steps that have been executed, any variable values viewed, and any error messages that may occur. This information is also displayed in the block at the bottom of the canvas.
 +  - Examine variable values (described below).
 +  - Undock from design canvas
 +  - Expand and refresh variable
  
 <WRAP center round info 80%> <WRAP center round info 80%>
-This window can be moved on the screen by “grabbing” the title bar and dragging the window to another position.+Things to consider when using the Test tool. 
 + 
 +  * If Bizweaver error notifications are in use, disable it while testing (turn off). If it is active, an "error" email will be generated any time the workflow is terminated, intentionally or not.  
 +    * Starting in Bizweaver 2.7 "disable during test" option in the notifications fly-out will disable error notifications during testing. 
 +  * Limit the number of records being passed into a loop.  This is particularly easy if the input is an SQLCommand: Reader step. 
 +  * Use breakpoints to stop at specific steps.
 </WRAP> </WRAP>
  
  
-Click button [**>**] to move from step to step. Or click button [**>>**] to automatically move through the workflow. The current step is highlighted in <color #ed1c24>red</color> as the processing progresses through the workflow. In the following image, the ‘current step” is “Loop_ProcessRecords.”+=====Breakpoints=====
  
-{{  :bw:introimage17.png?576x161  }}+Breakpoints are used when testing a workflow, and there is a need to stop at a specific step. Breakpoints can be set either in the workflow list view or by right-clicking a step and setting the breakpoint.
  
-<WRAP center round info 80%> +  * Breakpoints only affect workflow testing  
-Things to consider when using the Test tool. +  * They save when saving the workflow  
- +  * All breakpoints can be manipulated at once using the vertical ellipsis in the list view header. 
-  * If Bizweaver error handling is in use, disable it while testing.  If it is active an "error" email will be generated any time the workflow is terminated, intentionally or not. +    * Enable  
-  * Limit the number of records being passed into a loop.  This is particularly easy if the input is a SQLCommand: Reader step. +    * Disable 
-</WRAP>+    * Remove
  
 +{{ :bw2:bizweavernewtestrun3.png |}}
  
 ===== Examining Variables ===== ===== Examining Variables =====
  
-One of the key features of the Test Run tool is the ability to examine values during the workflow execution. This is done in the ‘Examine Variables” area at the top of the test run window.+One key feature of Testing a workflow is the ability to examine values during its execution. This is done in the ‘Examine Variables” area at the top of the test run window.
  
-There are two drop-down list windows in this area. The drop-down on the left lists workflow steps that have been executed. These are the steps from which values can be viewed+There are two drop-down list windows in this area. The drop-down on the left lists workflow steps that have been executed. These are the steps from which values can be viewed. The drop-down on the right shows the values (variables) that can be viewed for the selected workflow step.
  
-{{  :bw:introimage18.png?520x91  }} +{{ :bw2:bizweavernewtestrun5.png |}}
- +
-The drop-down on the right shows the values (variables) that can be viewed for the selected workflow step. In the following image the “SQLCommand_getData” step has been selected. +
- +
-{{  :bw:introimage19.png?520x142  }}+
  
 When a variable is selected, its value is displayed in the field to the right. This is the value that will be available to subsequent steps. When a variable is selected, its value is displayed in the field to the right. This is the value that will be available to subsequent steps.
  
-{{  :bw:introimage20.png?520x95  }}+{{ :bw2:bizweavernewtestrun4.png |}}
  
 Multiple values from multiple steps can be viewed at any time. Multiple values from multiple steps can be viewed at any time.
  
-{{  :bw:introimage21.png?520x93  }}  +Using {{:bw2:bizweavernewtestrun6.png|}} will either expand the variable to be viewed in its own window. Or refresh the variable. 
  
-Note that some variables are affected by the Bizweaver looping function. See the section named **//[[bw1:using_variables#Special Note for Step Variables and Loops|“Special Note for Step Variables and Loops”]]//** in the **//[[bw1:using_variables|“Bizweaver – Using Variables”]]//** document for more information. In these cases, the value displayed does not automatically change with each loop instance. The value must be refreshed by clicking the [>>} button for the desired variable.+Note that some variables are affected by the Bizweaver looping function. See the section named **//[[bw2:using_variables#Special Note for Step Variables and Loops|“Special Note for Step Variables and Loops”]]//** in the **//[[bw2:using_variables|“Bizweaver – Using Variables”]]//** document for more information. In these cases, the value displayed does not automatically change with each loop instance. The value must be refreshed by clicking the refresh button for the desired variable.
  
  
 ===== Test Run and Loops ===== ===== Test Run and Loops =====
  
-The Test Run tool executes each step of the workflow. If the workflow contains a loop, the tool will cycle through every record passed into the loop. For example, if the input list has 100 records, you will see the tool process the steps within the loop 100 times. In these cases, the “automatic” execution and execution speed tools are helpful.  Or. as noted earlier, limit the number of input records during the testing process.+Testing executes each step of the workflow. If the workflow contains a loop, the tool will cycle through every record passed into the loop. For example, if the input list has 100 records, you will see the tool process the steps within the loop 100 times. In these cases, the “automatic” execution and execution speed tools are helpful.  Or, as noted earlier, limit the number of input records during the testing process.
  
 ===== Test Run Results ===== ===== Test Run Results =====
  
-Test run information is written to text files during the processing cycle. These files are available at the end of the run via icons at the far-right end of the display area below the design canvas.+Test run information is written to a text file during the processing cycle. This file is available at the end of the run via the "Open in Notepad" button at the bottom of the workflow designer area below the design canvas. 
 +====Version 2.6==== 
 +**"Open in Notepad:"** Access this option will open the log of the workflow that just ran. 
  
-{{  :bw:introimage22.png?576x41  }}+{{ :bw2:bizweavertestrun8.png |}}
  
-Access these options before clicking on the test run display area, since this ends the test run cycle and the icons are no longer available.+**"View Last Button:"** Will open the last test run of the workflow. If the last run window is closed, it can be opened again by clicking this button.
  
-  * The top icon closes the test run display to end the execution cycle. Click in the test run display area does the same thing. +{{ :bw2:bizweavertestrun1.png |}} 
-  * The middle icon displays the steps that were executed. This is a text file and can be saved to another location if desired. + 
-  * The bottom icon displays additional information about execution of various components such as SQL connections, SQL commands, etc. This is a text file and can be save to another location if desired.+**"View Last Window:"** This will display all the information seen in the test run tool. This can be closed by clicking the "X" in the right corner of this window. 
 +{{ :bw2:bizweavertestrun10.png |}} 
 + 
 +====Version 2.7==== 
 + 
 +**"Open in Notepad:"** Access this option will open the log of the workflow that just ran.  
 + 
 +{{ :bw2:bizweavernewtestrun7.png |}} 
 + 
 +**"Running Log:"** This will now always be displayed after a test run was initiated. This window can be collapsed using the icon to the right of its window. 
 + 
 +{{ :bw2:bizweavernewtestrun8.png |}}
  
 These results are helpful when troubleshooting a workflow. Third Wave support may request that you send these logs if you report an issue. The log files can also be found in C:\Program Data\Bizweaver. These results are helpful when troubleshooting a workflow. Third Wave support may request that you send these logs if you report an issue. The log files can also be found in C:\Program Data\Bizweaver.
  
-===== Terminating a Test Run Cycle =====+===== Stopping a test =====
  
-A test run cycle can be terminated at any time by clicking the red **<color #ed1c24>X</color>** in the upper right corner of the Test Run Tool __display box__.+====Version 2.6==== 
 +A test can be stopped at any time by clicking the red outlined button **<color #ed1c24>Close</color>** in the lower right corner of the Test Run Tool __display box__.
  
-{{  :bw:introimage23.png?576x107  }}+{{ :bw2:bizweavertestrun9.png |}}
  
 A dialog to confirm that you want to end the test run is displayed. Click [**Yes**] to end the test run or [**No**] to continue with the test run. A dialog to confirm that you want to end the test run is displayed. Click [**Yes**] to end the test run or [**No**] to continue with the test run.
  
-An “error” message is displayed in the test run listing. This is normal and can be disregarded.+====Version 2.7==== 
 + 
 +A test can be stopped at any time using the "stop" icon in the toolbar. Once clicked, the test window will close, and the log with the last test runs details will be the only thing displayed.
  
-Click the red **<color #ed1c24>X</color>** again to end the test run processing.+{{ :bw2:bizweavernewtestrun9.png |}}
  
 <WRAP center round info> <WRAP center round info>
-As noted earlier, the test run process is actually executing the workflow steps. If you terminate a test run cycle, whatever has occurred will not be changed. For example, assume you have workflow steps that read a file and insert the records into a SQL table. Additional workflow steps then follow. If you terminate the test run after the SQL insertion step, those records are in the database and will remain there. The termination does not roll them back.+As noted earlier, the test process is actually executing the workflow steps. If you terminate a test, whatever has occurred will not be changed. For example, assume you have workflow steps that read a file and insert the records into a SQL table. Additional workflow steps then follow. If you terminate the test run after the SQL insertion step, those records are in the database and will remain there. The termination does not roll them back.
  
 </WRAP> </WRAP>
  
bw2/test_run_tool.1608059950.txt.gz · Last modified: 2020/12/15 14:19 by akoehler

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki