### Example Quality Center Connection Setup

Source: https://docs.testarchitect.com/user-guide/integration-with-third-party-tools/hp-quality-center/configuring-integration-with-hp-quality-center/setting-up-the-connection-with-quality-center/configuring-the-quality-center-connection

This example demonstrates a complete setup for the Quality Center connection parameters, including server URL, controller IP addresses, and enabling title comments.

```text
server=http://lgvn12989:4040/qcbin; machines= 192.168.167.68,192.168.167.69; title in comment=yes
```

--------------------------------

### Start Program Action

Source: https://docs.testarchitect.com/built-in-actions-reference/command-line/start-program

This section details the 'start program' action, which is used to launch a specified application on the test machine. It covers the required and optional arguments, along with various usage examples.

```APIDOC
## start program

### Description
Launch a specified application on the test machine.

### Method
Not Applicable (Action within TestArchitect)

### Endpoint
Not Applicable

### Parameters
#### Arguments
- **program** (String) - Required - The program to be started, prepended with its execution path, if necessary.
- **parameter** (String) - Optional - A parameter or string, such as the name of a data file, to be passed to the launched program. This is an invisible argument and requires a 'parameter' header.

### Request Example
#### Example - Case 1: Starting an application
##### Action lines
```
start program| C:\Program Files\LogiGear\TestArchitect\sample\CarRental\CarRental.exe
```

#### Example - Case 2: Starting an application that accepts an argument (Option 1: Using parameter argument)
##### Action lines
```
start program| "C:\Program Files (x86)\Notepad++\notepad++.exe"| "d:\test.txt"
```

#### Example - Case 2: Starting an application that accepts an argument (Option 2: Including argument in program argument)
##### Action lines
```
start program| "C:\Program Files\Notepad++\notepad++.exe" "d:\test.txt"
```

### Response
#### Success Response
None

#### Response Example
None

### Notes
- The **parameter** argument is invisible. To use it, specify its value and header in the cell to the right of the last visible argument.
- Alternatively, the parameter can be appended to the program argument, separated by a space.
- Full execution paths are not always necessary if the program's directory is in the system's execution search path (e.g., %PATH% on Windows, $PATH on Linux).
- This action supports the `<ignore>` modifier, which will skip the action if present in any argument's value or evaluated expression.
```

--------------------------------

### Start Application - Basic Example

Source: https://docs.testarchitect.com/built-in-actions-reference/command-line/start-program

Launches an application without any additional parameters. Ensure the program path is correctly specified.

```ActionScript
start program| C:\Program Files\LogiGear\TestArchitect\sample\CarRental\CarRental.exe
```

```ActionScript
check window exists| login
```

--------------------------------

### Pre-condition Section Example

Source: https://docs.testarchitect.com/built-in-actions-reference/error-handling/set-notice-level

Example of a pre-condition section that starts the Notepad application.

```Actionscript
start app_notepad
```

--------------------------------

### Example JSON for Multiple iOS Devices

Source: https://docs.testarchitect.com/automation-guide/application-testing/mobile-testing/testing-in-the-cloud/testarchitect-and-remote-testkit/testing-web-based-applications-on-safari-ios/creating-a-test/multiple-cloud-devices

This example demonstrates how to configure two concurrent iOS cloud devices for automated testing. Ensure the device names and platform versions are accurate for your setup.

```json
[{"Cloud Device 1": {"URL": "http://192.168.169.137:4725/wd/hub","platformName": "iOS","deviceName": "1eca0a6d5b22f68feedd6a780dcf1db0057ac28f","browserName": "safari","newCommandTimeout": "600","automationName": "XCUITest","platformVersion": "9.3"}},{"Cloud Device 2": {"URL": "http://192.168.169.137:4725/wd/hub","platformName": "iOS","deviceName": "002ebf12-a125-5ddf-a739-67c3c5d20177","browserName": "safari","newCommandTimeout": "600","automationName": "XCUITest","platformVersion": "10.1"}}]
```

--------------------------------

### Example Chrome Shortcut Target Command

Source: https://docs.testarchitect.com/user-guide/getting-started/sample-repository/scrum-board/preparing-web-browsers/preparing-google-chrome-for-web-testing/configuring-google-chrome

This is an example of the complete Target command line string after appending the required flags to the default Chrome executable path. Verify your path matches your installation.

```bash
"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="C:\Users\Public\LogiGear\TestArchitect\chrome_dir" --no-first-run --disable-web-security --enable-views-textfield --force-renderer-accessibility
```

--------------------------------

### GetSetting Usage Example

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/testarchitect-automation-classes/engine-class-methods/getsetting

Example showing how to call GetSetting with a default value.

```text
GetSetting(“language”, “user defined”, ““)
```

--------------------------------

### Start Function

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/testarchitect-automation-classes/engine-class-methods/start

Initializes TestArchitect by starting with specified settings and a data directory.

```APIDOC
## Start Function

### Description
Start TestArchitect.

### Method
integer Start (string filename, string directory)

### Parameters
#### Path Parameters
- **filename** (string) - Required - File with the initial values of various AbtLibrary settings.
- **directory** (string) - Required - The data directory, a directory that TestArchitect can use to create files in.

### Return Value
Return 1 if the call is successful; otherwise, 0. If unsuccessful, the diagnostic functions can be used to get more details.

### Notes
- This function has to be executed before any AbtLibrary function. It mainly initializes the internal data structures of TestArchitect.
```

--------------------------------

### Start an application

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/built-in-actions/system-actions/command-line/start-program

Basic usage of the start program action to launch an application.

```TestArchitect
start program | C:\Program Files\Notepad++\notepad++.exe
```

--------------------------------

### Repeat/Until Loop Example in TestArchitect

Source: https://docs.testarchitect.com/built-in-actions-reference/control-flow/repeat

Demonstrates the 'repeat' action to start a loop and 'until' to define the exit condition. Use this for iterative tasks where the number of repetitions is determined by a condition.

```TestArchitect
local variable| temp count| 1
repeat| |
| text| 
report| # temp count|
|  |
| name| value
local variable| temp count| #temp count+1
|  |
| condition to stop|
until| # temp count=2|
```

--------------------------------

### WIQL Query Example

Source: https://docs.testarchitect.com/TA_Help/Topics/ug_MTM_WIQL_reference.html

A concrete example of a WIQL query targeting specific IDs for a test plan, suite, and configuration.

```sql
SELECT * 
       FROM TestPoint
       WHERE PlanId=3160 AND 
       SuiteId=3189 AND 
       ConfigurationId=20
```

--------------------------------

### Method Syntax Declaration Examples

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/testarchitect-automation-classes/syntax-notations

Examples of method syntax declarations in TestArchitect compared to Visual Basic.

```text
AbtEntity OpenEntity(string Entity, [Boolean Refresh], [integer Seconds = -1])
```

```text
Function OpenEntity(Entity As String, Optional Refresh As Boolean, Optional Seconds As Long = -1) As AbtEntity
```

--------------------------------

### Example of a generated harness name

Source: https://docs.testarchitect.com/user-guide/controller-management

A concrete example showing how the naming convention is applied to a specific test execution.

```text
MultipleReservations (2018-07-03 11.09.47)- bmmtiq0jok0f
```

--------------------------------

### Get Screen Resolution Action Line

Source: https://docs.testarchitect.com/built-in-actions-reference/operating-system/get-screen-resolution

Example of calling the get screen resolution action within a TestArchitect test module.

```TestArchitect
                                  
---  
                                    | width| height  
get screen resolution| w| h  
                                  
```

--------------------------------

### get text content Action Line

Source: https://docs.testarchitect.com/built-in-actions-reference/optical-character-recognition/get-text-content

Example of an action line calling get text content to retrieve text from a control and store it in a variable.

```text
get text content| Encounter| document type| | text_content
```

--------------------------------

### Using get window property

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/the-test-language/expressions

Example of an action where the variable argument is not evaluated, as it is intended for assignment.

```TestArchitect
                          window    property    variable
get window property       login     title       logtitle
```

--------------------------------

### Start an application with parameters

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/built-in-actions/system-actions/command-line/start-program

Launching an application with command-line arguments using either the parameter argument or by appending to the program path.

```TestArchitect
start program | C:\Program Files\Notepad++\notepad++.exe | C:\temp\test.txt
```

```TestArchitect
start program | C:\Program Files\Notepad++\notepad++.exe C:\temp\test.txt
```

--------------------------------

### Execute JavaScript: Hello World

Source: https://docs.testarchitect.com/built-in-actions-reference/browsing/exec-script

This example demonstrates the basic usage of the 'exec script' action to write 'Hello World' to a web page using JavaScript.

```TestArchitect
exec script| JavaScript| document.write("Hello World")
```

--------------------------------

### Invoke help for a specific command

Source: https://docs.testarchitect.com/user-guide/import-export-command-line-tool/help-command

To get help on a specific command, append the command name after the --help option. For example, to get help for the ImportRepository command, use the following syntax.

```bash
java -jar TAImportExportTool.jar --help [--<CommandName>]
```

```bash
java -jar TAImportExportTool.jar --help ImportRepository
```

--------------------------------

### Start Program Action

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/built-in-actions/system-actions/command-line/start-program

Launches a specified application on the test machine. Supports arguments and platform-specific notes for Android and iOS.

```APIDOC
## start program

### Description
Launch a specified application on the test machine.

### Method
Not Applicable (Built-in Action)

### Endpoint
Not Applicable (Built-in Action)

### Parameters
#### Arguments
- **program** (string) - Required - The program to be started, prepended with its execution path, if necessary. For mobile devices: Android - the application package name. iOS - the application name.
- **parameter** (string) - Optional - A parameter or string, such as the name of a data file, to be passed to the launched program. This is an invisible argument and requires a separate header.

### Request Example
Not Applicable (Built-in Action)

### Response
Not Applicable (Built-in Action)

### Valid contexts
This action may be used within the following project items: test modules and user-defined actions.

### Notes
- iOS: To ensure that start _program_ can successfully launch an application on an iOS device, refer to Launching an AUT.
- **program** argument:
  - For an iOS device, the **program** argument should hold the name of the running application itself, e.g. _Car Rental_. If needed, you can obtain the application’s name through the Interface Viewer by checking the **name** property in the **Properties** panel of the **TA Properties** tab and removing the appended 'Normal Z1' string.
  - On an Android device, **program** is the package name of the running application. This can be obtained from the Android Instrumentation Tool dialog box.
- **parameter** argument:
  - **parameter** is an unsupported argument and hence invisible. To use it, you must specify both its value and header, in the cell to the right of last visible argument.
  - An alternative to using the **parameter** argument is to simply append its contents to the **program** argument, delimited by a space.
- For the execution path, you may use the standard execution file path format of the operating system. Forward slash delimiters are supported regardless of operating system.
- A full path is not required if the directory in which the program resides is listed in the execution search path environment variable of the operating system.
- On iOS devices, a full path is not required even if your app is grouped under an app folder; only the app’s name is required.
- This action supports the `<ignore>` modifier. If the string `<ignore>` is present as the value of any of the arguments, or any argument contains an expression that evaluates to `<ignore>`, the action is skipped during execution.

### Applicable Built-In Settings
The following settings are applicable to this action: remove double quotes from cells.

### Example - Case 1: Starting an application
```
Action Lines
start program

Result

```

### Example - Case 2: Starting an application that accepts an argument
Say you want to open a text file with the _Notepad++_ application. Since _Notepad++_ accepts the path of a text file as a command line argument, we can specify the file when we launch the application. We have two options for doing this.

Option 1: Using the **parameter** argument:
```
Action Lines
start program	parameter	C:\MyData\MyFile.txt

Result

```

Option 2: Including the argument to the application in the **program** argument:
```
Action Lines
start program	C:\Program Files\Notepad++\notepad++.exe C:\MyData\MyFile.txt

Result

```

### Example - Case 3: Starting an application on an iOS device
```
Test Lines
start program	Car Rental

Result

```
```

--------------------------------

### Navigate to a local HTML file

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/built-in-actions/user-interface-actions/browsing/navigate

Example showing the required file protocol syntax and whitespace encoding for local file paths.

```text
file:///C:/Program%20Files/LogiGear/TestArchitect/samples/ScrumBoard/index.html
```

```text
file://///lgvn10003
```

--------------------------------

### instr Function Example

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/the-test-language/functions/string-functions/instr

Illustrates the usage of the instr function to find the starting position of a substring within a larger string.

```action-based testing language
Test Lines
  

Result  
  

* * *
```

--------------------------------

### start program

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/built-in-actions/system-actions/command-line

Initiates the execution of a program on the host computer.

```APIDOC
## start program

### Description
Starts a program on the host computer.

### Method
ACTION

### Endpoint
start program
```

--------------------------------

### Execute slide action in TestArchitect

Source: https://docs.testarchitect.com/built-in-actions-reference/device/slide

Example of the slide action line within a test module, specifying start and end coordinates and the duration in milliseconds.

```text
slide| 80| 520| 360| 470| 600
```

--------------------------------

### StartRun Method

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/testarchitect-automation-classes/engine-class-methods/startrun

Initializes a test run using a specified cluster file.

```APIDOC
## StartRun

### Description
Prepares the execution of a test cluster. This function must be called before NextAction can be executed.

### Syntax
`integer StartRun (string filename)`

### Parameters
- **filename** (string) - Required - The name of the cluster file.

### Return Value
- **integer** - Returns 1 if the call is successful; otherwise, 0. If unsuccessful, diagnostic functions can be used to retrieve more details.
```

--------------------------------

### Get Clock Count Action

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/built-in-actions/test-support-actions/timing/get-clock-count

Retrieves the elapsed time since the most recent execution of a start clock count action. This is useful for performance monitoring.

```APIDOC
## GET CLOCK COUNT

### Description
Retrieve the elapsed time since the most recent execution of a start clock count action.

### Method
GET (Implicit, as it's an action within a test script)

### Endpoint
N/A (This is an action within TestArchitect)

### Arguments
#### Path Parameters
None

#### Query Parameters
None

#### Request Body
None

### Request Example
None

### Response
#### Success Response (Implicit)
- **variable** (string) - Variable to receive the elapsed time (units: milliseconds).

#### Response Example
None

### Notes
- Use this action, paired with start clock count to ascertain the performance of your test, or a segment of it.
- The TestArchitect timer runs continuously across action calls and test modules of the same test run (whether in serial runs or run test invocations), with its value globally available to the get clock count action.
- Execution of get clock count only samples the TestArchitect performance timer, it does not stop or reset it. Hence, multiple invocations of get clock count following a single start clock count may be used as multiple timing “checkpoints”.
- variable argument:
    - If the variable in argument `variable` has not been declared, the action creates it as a global.
    - If the variable argument is left empty, TestArchitect supplies a global variable with the name `_result`.
- This action supports the `<ignore>` modifier. If the string `<ignore>` is present as the value of the argument, or the argument contains an expression that evaluates to `<ignore>`, the action is skipped during execution.

### Applicable Built-In Settings
- remove double quotes from cells

### Example
Action Lines

```
start clock count
// ... some actions ...
get clock count(my_elapsed_time)
```

Result

`my_elapsed_time` will contain the elapsed time in milliseconds.
```

--------------------------------

### Complete TestInitialized Implementation

Source: https://docs.testarchitect.com/user-guide/integration-with-third-party-tools/tfs-integration/additional-features-of-tfs-mtm/ta-tfs-extensibility/workflow-example-of-using-ta-tfs-extensibility

Full implementation example for the TestInitialized method, combining repository configuration, test ID settings, and startup settings.

```csharp
/// <summary>
/// code to be run after TestInitialize
/// </summary>
         
[TAExtensibilityMethod(LoaderConstant.TestInitialized)]
         
public void TestInitialized(TAExecutionArguments e)
{
   ITAExecution execObj = TAIntegrationLoader.Instance.ITAExecution;
         
   execObj.ExecutionInfo[TAExecutionConstant.RepositoryServer] = "localhost";
   execObj.ExecutionInfo[TAExecutionConstant.RepositoryName] = "SampleRepository";
   execObj.ExecutionInfo[TAExecutionConstant.RepositoryPort] = "53400";
   execObj.ExecutionInfo[TAExecutionConstant.ProjectName] = "Car Rental";
   execObj.ExecutionInfo[TAExecutionConstant.UserName] = "administrator";
   execObj.ExecutionInfo[TAExecutionConstant.Password] = "";
   
  ((TestContext)e.TestContext).Properties[TAExecutionConstant.UseTestIDForUploadedResults] = "Yes";

   List<StartupSetting> listStartupSettings = new List<StartupSetting>();
         
   StartupSetting browser = new StartupSetting("use browser", "chrome", "default browser", StartupSettingType.BUILT_IN_SETTING);
   StartupSetting AUT = new StartupSetting("path", "D:\Sample.exe", "AUT path", StartupSettingType.USER_DEFINE_SETTING);
         
   listStartupSettings.Add(browser);
   listStartupSettings.Add(AUT);
         
   execObj.ExecutionInfo[TAExecutionConstant.StartupSettings] = listStartupSettings;
   execObj.ExecutionInfo[TAExecutionConstant.StartupSettingsMode] = "yes";
         
   execObj.Save();
}
```

--------------------------------

### Check Tree Node Exists - Numerical Index Example

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/built-in-actions/user-interface-actions/tree-view/check-tree-node-exists

This example shows how to use the 'check tree node exists' action with a node path specified by numerical indices. Indices start at 1. Use quotation marks for text values that might be mistaken for indices.

```ActionScript
check tree node exists
  window=win_main
  tree=tv_file_explorer
  node path=1/2/3
```

--------------------------------

### Get List Cell Value Action

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/built-in-actions/user-interface-actions/list-table-grid/get-list-cell-value

This section details the 'get list cell value' action, which retrieves the text content of a cell in a list view. It includes information on arguments, valid contexts, notes on variable handling, applicable settings, applicable controls, and an example.

```APIDOC
## GET LIST CELL VALUE

### Description
Retrieve the text content of a cell in a list view.

### Method
Not Applicable (This is an action, not an API endpoint)

### Endpoint
Not Applicable

### Arguments
#### Path Parameters
None

#### Query Parameters
None

#### Request Body
None

### Parameters
- **window** (string) - Required - TA name of the window.
- **list** (string) - Required - TA name of the control.
- **item** (integer) - Required - Row number of the cell. (Row numbers start at 1, exclusive of any header row.)
- **column** (integer) - Required - Column number of the cell (Column numbers start at 1).
- **variable** (string) - Optional - Variable to receive the returned value.

### Request Example
None (This is an action within a test script)

### Response
#### Success Response (200)
- **_result** (string) - The text content of the specified cell, or the value assigned to the specified variable.

#### Response Example
None (Action execution results are stored in variables)

### Valid contexts
This action may be used within the following project items: test modules and user-defined actions.

### Notes
- **variable argument**:
  - If the variable in `variable` has not been declared, the action creates it as a global.
  - If the `variable` argument is left empty, TestArchitect supplies a global variable with the name `_result`.
- This action supports the `<ignore>` modifier. If the string `<ignore>` is present as the value of any of the arguments, or any argument contains an expression that evaluates to `<ignore>`, the action is skipped during execution.

### Applicable Built-In Settings
case sensitive, ignore blank space, remove double quotes from cells, standard ASCII only, item wait, object wait, value changed wait, window wait, load invisible controls.

### Applicable Controls
list view
```

--------------------------------

### Start Application with Parameter (Option 1)

Source: https://docs.testarchitect.com/built-in-actions-reference/command-line/start-program

Launches an application and passes a file path as a parameter using the 'parameter' argument. The 'parameter' argument is invisible and requires its header to be specified.

```ActionScript
start program| "C:\Program Files (x86)\Notepad++\notepad++.exe"| "d:\test.txt"
```

```ActionScript
check window exists| home
```

--------------------------------

### Click Window Action Line Example

Source: https://docs.testarchitect.com/built-in-actions-reference/mouse/click-window

This action line demonstrates how to use the 'click window' action with specific coordinates and click type. Ensure the window is available and coordinates are within bounds.

```TestArchitect
click window| view cars| 120| 150| left
```

--------------------------------

### Retrieve table column count in TestArchitect

Source: https://docs.testarchitect.com/built-in-actions-reference/list-table-grid/get-column-number

Example showing how to use the get column number action to store the column count of a table into a variable and verify it.

```TestArchitect Action Lines
                                  
---  
                                    | interface| |   
use interface| Car Rental| |   
 | | |   
| window| control| variable  
get column number| view orders| orders table| i  
 | | |   
| value| expected|   
check value| #i| 14|   
                                  
```

--------------------------------

### Implement IExtensionPackage Interface

Source: https://docs.testarchitect.com/testarchitect-tutorial/part-3-extending-testarchitect/lesson-10-wpf-extensibility/scenario/wpf-extensibility-solution/creating-an-extension

This is the entry point for a TestArchitect extension. It requires implementing the IExtensionPackage interface from ExtensionLib.

```csharp
public sealed class WpfExtensionPackage : IExtensionPackage 
{
    //Insert implementation code here
}
```

--------------------------------

### Get Text Coordinates with Index

Source: https://docs.testarchitect.com/built-in-actions-reference/optical-character-recognition/get-text-coordinates

This example demonstrates finding the second instance of a text string ('TestArchitect') within the 'home' control. The 'index' argument is crucial for specifying which occurrence to retrieve.

```action
--- |
        | window| control| rect| text| index| left| top
get text coordinates| home| | | TestArchitect| 2| l_Pos| t_Pos
```

--------------------------------

### Test Procedure Example

Source: https://docs.testarchitect.com/automation-guide/application-testing/testing-web-and-ria-applications/testing-web-applications/automated-web-testing-with-non-webdriver/getting-started-with-web-testing

An example test procedure demonstrating the handling of prompt and alert popups using 'enter text on next popup' and 'click on next popup'.

```TestArchitect
enter text on next popup
click on next popup
click
enter text on next popup
check popup message
check popup message
```

--------------------------------

### Retrieve and verify status bar value in TestArchitect

Source: https://docs.testarchitect.com/built-in-actions-reference/browsing/get-status-bar-value

Example showing the usage of get status bar value to capture text into a variable and check status bar value to verify it.

```TestArchitect Action Lines
                                  
---  
                                    config| |   
 | |   
navigate to web| |   
 | |   
| window| variable  
get status bar value| home page| s  
 | |   
| window| expected  
check status bar value| home page| Done  
```

--------------------------------

### Get Context Menu Item State - Numerical Index

Source: https://docs.testarchitect.com/built-in-actions-reference/toolbar-menu-scrollbar/get-context-menu-item-state

Retrieves the state of a context menu item using its numerical index. The index starts at 1. Ensure the 'search' window and 'songs list' control are accessible.

```action
get context menu item state| search| songs list| 5| state
```

--------------------------------

### Get Picture Location - Case 2: Rect Argument Specified

Source: https://docs.testarchitect.com/built-in-actions-reference/picture-handling/get-picture-location

This example demonstrates specifying a rectangular area for the search. The search for the picture is limited to the defined 'rect' dimensions within the active UI element.

```Action Line
--- |
| picture | window | control | rect | index | left | top | width | height
get picture location | /login button | login | login | 1,1,100,100 | | l_Pos | t_Pos | w_Pos | h_Pos
```

--------------------------------

### Example: Importing Test Modules with Picture Checks

Source: https://docs.testarchitect.com/user-guide/import-export-command-line-tool/importtoid-command

This example demonstrates how to import test modules, including their associated regular picture checks, into a TestArchitect project. Ensure the source file is a .zip archive containing the test module.

```bash
java -Dfile.encoding=UTF-8 -jar TAImportExportTool.jar --ImportToID --server "your_server_ip" --port 53400 --uid "your_username" --pwd "your_password" --repoName "your_repository_name" --projectName "your_project_name" --sourceFile "C:\\path\\to\\your\\test_module.zip" --ID "your_test_module_id" --overwrite true --includePictureChecks yes
```

--------------------------------

### Execute Test Steps with Various Actions

Source: https://docs.testarchitect.com/built-in-actions-reference/picture-handling/check-picture

This snippet demonstrates a sequence of TestArchitect actions including starting a program, clicking controls, navigating tree nodes, getting control properties, and finally checking a picture. It's used to automate UI interactions and verify visual elements.

```Action Lines
setting| verify picture| yes| | | | | |

| program| | | | | | | |
start program| C:\Program Files\LogiGear\TestArchitect\samples\CarRental\CarRental.exe| | | | | | | |

| window| control| click type| | | | | |
click| login| login| left| | | | | |
click| welcome| view cars| left| | | | | |

| window| tree| node path| type| | | | |
click tree node| view cars| car select tree| Car Types/Standard/Chevrolet Monte Carlo| left| | | | 

| window| control| property| variable| | | | |
get control property| view cars| car image| width| control_width| | | | |
get control property| view cars| car image| height| control_height| | | | |

| window| control| name| question| left| top| width| height
check picture| view cars| car image| chevrolet| Is it a yellow chevrolet?| 0| 0| # control_width| # control_height
```

--------------------------------

### Run TestArchitect Installer in Record Mode

Source: https://docs.testarchitect.com/user-guide/getting-started/installing-testarchitect-in-silent-mode/creating-an-installation-response-file

Execute the TestArchitect installation file with the /r flag to record installation settings for a silent installation. Ensure the path is quoted if it contains spaces.

```bash
"D:\Silent installation\TestArchitect Build\TestArchitect_8.3.0.143_x64.exe" /r
```

--------------------------------

### GetSetting Syntax

Source: https://docs.testarchitect.com/automation-guide/action-based-testing-language/testarchitect-automation-classes/engine-class-methods/getsetting

The signature for the GetSetting method.

```text
string GetSetting(string settingName, string settingType, string defaultValue)
```