Wilson Mar bio photo

Wilson Mar


Email me Calendar Skype call

LinkedIn Twitter Gitter Instagram Youtube

Github Stackoverflow Pinterest

Model-based functional testing through the lifecycle

US (English)   Español (Spanish)   Français (French)   Deutsch (German)   Italiano   Português   Estonian   اَلْعَرَبِيَّةُ (Egypt Arabic)   中文 (简体) Chinese (Simplified)   日本語 Japanese   한국어 Korean


This article contains my notes about learning and using Tricentis Tosca for continuous functional testing.

NOTE: Content here are my personal opinions, and not intended to represent any employer (past or present). “PROTIP:” here highlight information I haven’t seen elsewhere on the internet because it is hard-won, little-know but significant facts based on my personal research and experience.

The unique contribution of this article is a maticulously sequenced concise yet deep presentation, with PROTIPs along the way, so you can quickly come up to speed with the product. All one this one page to simplify text search.

CAUTION: This article is being constructed as of May 20, 2019.

Tricentis The company

On Glassdoor 66% of employees would recommend Tricentis to a friend and 82% approve of the (Stanford MBA) CEO Sandeep Johri (as of this writing).

  • Wolfgang Platz, Founder & CPO, Tricentis
  • Wayne Ariola, Marketing

Tricentis is based in Austria (Leonard-Bernstein Straße 10, 1220 Vienna). In the United States, Tricentis has an office in Jersey City and Silicon Valley. It also has a presence in Australia, Belgium, Denmark, Germany, India, Netherlands, Singapore, Switzerland, Poland, and the UK.

  • Get in Touch Live Chat</a>

PROTIP: The company does not allow communication with consumer email accounts such as gmail, hotmail, outlook, etc.


Each year the company hosts conferences in San francisco in the Spring and Vienna in the Fall.

Register for the live stream

The conference has a mobile app “Tricentis Accelerate” (by Attendify). An event code is given to those registered.


Consulting supporters:

  • Jeff Wilkinson, Managing Director, Accenture
  • Ramesh Pai, Global Head, NextGen QA, Wipro

Competition for Software Test Automation

Tricentis is the only vendor to achieve “leader” status in all three top analyst reports (i.e., the “Triple Crown.”).


Tosca is called a “model-based” test automation tool because automated tests are conducted based a database of metadata (technical information) extracted from the application under test during scans.

Because test cases are generated from the model, changes in the app’s model (requirements) all impacted test cases can be automatically updated as well. This tremendously reduces test case maintenance.

The model approach also enables makes RPA (Roboticc Process Automation) more reslient.

  • Tom Murphy, Sr. Director Analyst at Gartner

Being able to work on the model rather than script programming “democratizes” who can work on testing and automation. Business experts to contribute to test automation as well as eliminate the maintenance burden that erodes most test automation initiatives. Instead of programming a test automation framework, you scan the application’s UI or API to create a business-readable automation model.

The Tricentis USP (Unique Selling Proposition) is that Tosca’s “codeless” UI means “non-programmers” can “rapidly create and manage sophisticated end-to-end tests —- without technical resources” – and focus on business processes, workflows, and other business data.

My take however, is that testing is still “sophisticated” and requires someone interested in intracacies rather than magic simplicity.

Customers in the wild

Tricentis has identified customers as including global enterprises such as Allianz, ANZ Bank, Cisco, Dolby, Experian, First Data, HSBC, Merck, Office Depot, Samsung, Swiss Re, Starbucks, Telstra, UBS, Vodafone, Whole Foods, and WorldPay. Testimonials by customer employees:

  • Credit Karma - Ash Coleman, Head of Diversity & Inclusion,
  • Anthem - Adam Satterfield, Director of Testing & Quality
  • BNP Paribas - Philippe Buron


Tosca’s architecture enables Tosca to enable resilient test automation—for 150+ technologies, including SAP.

In May 2019 Tricentis bought LiveCompare for SAP change impact analysis from IntelliCorp, a pioneer smart systems company.

Tosca Commander has a SAP Solution Manager 7.2 Integration.


Version 12.2 introduces a new Salesforce Engine 3.0 for automating Lightning UI, which also inclues scanner.


  1. A matrix of links to documentation for each specific version is at:


    Click the “Enter” under the Online heading associated with each version, for an URL such as this for version 12.1:


    PROTIP: Use the online rather than off-line because if you have a question, you would have a ready URL to a specific page that can be easily shared with Support and others.

    Alternately, off-line after download:

  2. Create a folder on your machine to hold documentation files and cd into it.
  3. Get to the documentation download page at:


  4. Click to download “Tricentis Tosca 12.1 Documentation.zip” (the latest version as of this writing).

  5. Switch to Finder and Unzip the file “Tricentis Tosca 12.1 Documentation.zip” to a folder which contains a website.
  6. Delete the zip file.
  7. Delete folder “Tricentis Tosca 12.1 Dokumentation_de” if you don’t read German.
  8. Click to open folder “Tricentis Tosca 12.1”, “EN”.
  9. Unzip file “Tricentis Tosca 12.1 Documentation_en.zip”.
  10. Delete the zip file.
  11. Click to open folder “Tricentis Tosca 12.1 Documentation_en”.
  12. Click “index.htm” to open the website.


  13. Repeat above for folder “Tricentis_TDM_Studio_12_1”.

    PROTIP: TDM (Test Data Management) is the older feature superceded by TDS (Test Data Service), both of which save data in a database system such as SQLite. The TDM icon has a gray bar vs. clear gap in the TDS icon. Pulling data from a database enables real-time integration with other systems which updates the same database, such as a dynamic status of “Active” or “Inactive”.

  14. Repeat for “Tricentis_Analytics 12.1_Documentation.zip” Analytics is made available with the Enterprise license, which comes with a Qlic visualization tool license.

Test Requirements management

Tosca purchased qTest as part of the QASymphony acquisition in 2019.

Support QASymphony

QTest also integrated with TOSCA to meeting FDA traceability requirements for signature approvals.

Tosca features

This diagram at the academy login page pro


Tosca architecture components


Tosca Commander components:

  • Requirements Management (icons)
  • TestCase Design
  • TestPlanning
  • Reporting
  • Test Data Management (TDM) communicates with a TDM Repository
  • Tosca CI Remote Execution Service communicates with a Tosca CI Client on a Build server
  • Tosca Distribution Agent coordinates with Tosca Server and License server

Tosca (IIS) Server has a REST API Service and Tosca Workspaces working with the License Server and Tosca Connect.

  • Tosca Administration (Admin.) Console
  • DEX (Distributed Execution) communicates via DEX Agent to TCAPI
  • TDS (Test Data Service) Web Service

  • Tosca Event Monitor
  • Tosca Distribution Server
  • Exploratory Testin Server connects to
  • REST API Service
  • Tosca Data Service communicates with Tricentis Tosca vis https
  • Interactive Testing Server
  • Tosca Analytics via TCAPI

Bottom-up Component and Workflow description:

  • ActionModes steer test objects. ActionModes define how the value in the Value field should be applied for XTestStepValues in order to steer the control. ActionModes available to an XTestStepValue depend on the InterfaceType of the referenced XModule. Input values needed more than once can be buffered using the ActionMode Buffer or saved to a global variable buffer.

  • Classic engines use Modules to steer tests of legacy apps such as PowerBuilder through their custom ports. Classic modules are used to steer mainframe and older Excel spreadsheets.

  • Engine 3.0 use XModules steering modules created by XScan and Tosca Recorder for both Graphical User Interface (GUI) tests and non-GUI tests. The TBox framework contains (tree-like) hierarchically structures XModules to steer test objects.

  • Tricentis Tosca Mobile Engine 3.0 (which replaces Tosca Mobile+) automates testing of mobile applications running on smart phones, tablets, and Android emulators and iOS simulators.

  • Tosca OSV (Orchestrated Service Virtualization) works through an OSV Addin to Tosca Commander communicating via SOAP to an OSV Host talking to OSV Database and OSV Monitor talking to License Server.
  • Tosca BI (Business Intelligence)
  • Tosca Commander interacts with a Windows Active Directory (via TCP & UDP) to connect Tosca Workspaces with a Common Repository using TCAPI
  • Tosca Commander Interactive Testing communicates with the Interactive Testing Server and Interactive Testing Agent.

Tricentis Academy for Learning


About the Tricentis Academy

  1. All Tosca’s videos are stored in Vimeo and YouTube channel and also referenced from Tosca’s videos web page.

    BLAH: Vimeo does not provide users with speed controls like YouTube does.

Customers who paid for Platinum (aka Enterprise) licenses access all trainings for free.

Certification Classes

Initial core certification classes are free, but higher-level certifications are $149 each at

https://www.tricentis.com/academy/training-certifications has several tracks:

Core classes:

  • Automation Specialist Level 1 & 2 (AS1 and AS2) is the prequesite to either
  • Automation Engineer Level 1 & 2 or
  • Test Design Specialist Level 1 & 2
  • Test Architect 1 certification can be taken after passing all the above.
  • qTest Specialist

Specialty classes:

This diagram at the academy login page shows an OBSOLETE progression of certifications:


Initial certifications

Tricentis Automation Specialist 1 Self-Paced Track Standard course in 20-25 hours covers HTML control recognition, design automated test cases, automation features, and final execution. Participants construct five automated GUI test cases that covers control recognition, usage of steering parameters and dynamic values, execution on different browsers, and reusing modules.

  1. At https://support.tricentis.com/community/product.do?number=WIT0001016 click “Add to cart” (make sure the that “Product” appears briefly on the right)
  2. Go to Cart, check “I have read and agree to the Terms and Conditions”, Checkout.
  3. Click “OK” to the “successful” pop-up.
  4. Type your email and click “Redeem”. Click Yes to confirm.
  5. Review course details:
    Identifying HTML controls Creating HTML Modules Modifying steering properties
    Modifying steering properties
    Use of premade Tricentis Modules Best practice tips and exercise
    Test case structure
    Adding TestSteps and Test StepValues
    Handling dynamic values
    Verifications, test parameters
    Creation and use of a Libraries, TestStepBlocks
    Best practice tips and exercises
    Executing test cases and results analysis
    Cross browser options for test execution
    Table steering with constraints
    Fire events Linking to business requirements
    Recovery scenarios
    Recovery scenarios Best practice tips and exercises
  1. The Sample System Under Test is a Web Shop application at:


  2. Right-click to View Page Source. Notice <!DOCTYPE html> indicates it’s a HTML5 app.

  3. The tutorial goes over these test cases:

    1. Shipping Costs (core skills)
    2. Payment Process
    3. Discount Code
    4. Reorder
    5. Total Price all Orders
    6. Additional challenges

Automation Specialist 2 covers XML and Web Services test automation (REST API testing) using test case templates. Automation Specialist 2

    Data Driven TestCases
        TestSheets as a centralized data source
        Template concept
        Template conditions
        Run and Report Automated Data Driven TestCases
        Hands-on exercises
    Data driven API TestCases
        Web services and API concep
        Build API TestCases
        API Testing Templates
        Hands-on exercise
    Additional Learning Material
        Build your own data driven test

API References:

Tosca Guided Example Project v9.2 in page 2 of https://support.tricentis.com/community/downloads.do

Automation Specialist Practitioner training

The Automation Specialist Practitioner course is delivered over 2-day on-site by a certified Practitioner Trainer as an instructor-led hands-on coaching session that builds on core skills developed in Tricentis online trainings with skills to apply on a custom (your own) SUT (System Under Test) and its unique requirements. The coaching session is delivered on site . Topics include the Tosca Ecosystem, Troubleshooting.

The one-hour exam for this allows for a single try (60%), but open book.

Windows Installation

The following is based on this page.

A Mac can only be used with a virtual server instance running Windows.

  1. The Tosca Server is installed on Windows using local administrator rights. So make sure you have that associated with the user account being used.

    Once the Windows server instance is available…

  2. Install the latest Windows updates of the category Critical (Windows 7, 8) or Quality (Windows 10).

    .NET Framework

  3. Open the Firefox internet browser.
  4. Install Microsoft® .NET Framework Version 4.7.1 from:


  5. Click Download. Save file.

    Within an Amazon Workspaces instance, Downloads would be in

  6. When download is completed, double-click on the downloaded file to install to a folder named like:


  7. Click Yes to allow file to make changes.
  8. “I have read …” and click Install.
  9. Restart.

    Environment Variables

    On Windows 10:

  10. Click the Search icon. Type “Adv” to select “Advanced System Settings” of “Control Panel”.
  11. Click “Environment Variables…”. In section “System Variables”, click “New…”.
  12. Type in Varible Name: TRICENTIS_PROJECTS with value such as C:\Tosca_Projects for where Tosca project data is stored. On cloud instances, specify


  13. Click “OK”.


  14. Still in “Environment Variables…”, again click “New…”.
  15. Type in Varible Name: TRICENTIS_HOME with value for where Tosca project data is stored, such as:

    C:\Program Files (x86)\TRICENTIS\Tosca Toolsuite"

    NOTE: The 64-bit Tosca Commander are installed with standard AddIns (Tosca Requirements, Tosca TestCase-Design, Tosca Reporting, and Tosca Structured Objects).

    These run in either 32 (*X86.exe) or 64-bit mode, depending on whether Tosca Commander is started in a 64-bit or 32-bit operating system.

  16. Click “OK”.

    Download installer

    VIDEO: says from the Support page, select Downloads from the top menu:



    BLAH: I don’t see installer exe files. Support told me to:

  17. Highlight this “Free Trials” URL to pasting inside the Windows machine:


  18. Click “Start Free Trial” under “Tosca”.
  19. Enter your email and click “Get Started”.
  20. Click “Save File” in the pop-up.
  21. While you wait for the download to finish, viewing progress depends on the browser. On Firefox, click the icon at the upper-right corner:


    Version 12.1 is 1.0 GB.

  22. Double-click on the Tosca Commander executable named TOSCAversion number.exe such as TOSCA12.1.exe.
  23. Click OK to install Microsoft pre-requisites.

  24. Click “Next”.
  25. Check “I accept the terms in the license agreement”, then “Next”.
  26. To avoid connections, uncheck “Help improve Tricentis…”, “Next”.
  27. The default folder to install is

    C:\Program Files (x86)\TRICENTIS\Tosca Testsuite

    Variable TRICENTIS_HOME is where executables are installed. The following 64-bit executable files installed are processor-independent:

    • TOSCACommander.exe
    • TCShell.exe
    • DbRepositorySchemaMigrator.exe

  28. Click OK.
  29. Click Next.
  30. Click Next to default “Tosca Commander”.
  31. Click Install. Wait several minutes for it to finish.
  32. Check “Check to restart after setup completion”, then click Finish.
  33. Click “Yes” to confirm restart.
  34. Reconnect if you’re running a virtual instance.
  35. When the machine boots up again, click the Windows icon to see the Tosca programs installed:


    The Tosca Commander agent is installed on Windows machines to invoke tests and receive results.

Get Product License

NOTE: Instructions below are based on Tosca version 12.1.

Instead of getting a Tricentis Tosca Testsuite 14-day Trial license here.

  1. Verify your email address.
  2. Tosca’s Support Portal provides links to articles, discussions, documentation, support incidents, search, , etc. at:

    https://support.tricentis.com/community/home.do?verify=s for

  3. Request a training license by clicking on the email or at:


  4. Choose on-premise or a cloud license (while logged on) for:


    Go directly to the above URL if you already requested a license.

  5. Click the icon on the same line as “Premium Package” to copy the license key text.

  6. Access the Tosca cloud license server Tricentis_Academy_Cloud.


  7. Access the Tosca cloud license server Tricentis_Academy_Cloud.

    https://support.tricentis.com/community/article.do?number=KB0013085 Knowledge Base article

    Connect to a local license server

    VIDEO: How to Activate your Trial from inside Tosca Commander.

  8. Click the Windows icon and click “Tosca License Configuration”.
  9. Click Activate.
  10. Click Local Machine. OK.
  11. Switch to the license port

  12. Open Tricentis Tosca Commander, navigate to the Project menu and click on License. Click on Connect.

Ability to access the cloud server through the port TCP 443.

License Server installation process [The TCP port is set to 7070 by default]

Training Course Access

  1. To access the class in the Support Portal, click on “My Assets” -> Academy at URL:


    Password field must be less than 20 characters.

  2. Click “My courses”.
  3. Click “Open Curriculum” for Level 1 or 2.
  4. Click “Launch” associated with the top lesson without a gree check icon.

    PROTIP: To speed up videos, click the gear icon and instead of “Normal”, select “1.5”.

    PROTIP: Use an additional monitor so you can see the tutorial on one screen and your notes in another screen.

    PROTIP: An error occurs if a user opens the course in more than one browser window.


  1. Open Tosca Commander from Windows.

  2. Create a new workspace.

    When a workspace is created with “Use workspace template” checked, Subset Default objects are automatically imported or via the option Import Subset in the file is located at:


    The newer format Standard.tsu file (default objects) contains Modules, pre-defined Virtual Folders, and Standard Reports.

    A subset is a file containing Tosca artifacts which can be shared with other projects using import and export. These have file extension “.tsu”, such as:

          AutomationSpecialistI_BaseSubset.tsu (dated Feb 2, 2017).

    PROTIP: *.tsu files are binary format which can only be read by (imported into) Tosca.

    Prior versions stored subset files with extension .tce. There is no conversion utility.

    JSON files (documents) are loaded into Resources for manipulation. Resources require unique names to be assigned to them. Resources can be used multiple times within the same TestCase. When test execution finishes, used resources are discarded and can no longer be used across multiple TestCases.

    Each TestCase describes the sequence used for the verification of properties defined in specifications: the entries needed for the execution of the TestCase; the expected output or reactions to the entries on the part of the application to be tested; the expected follow-up conditions that result from the execution of the TestCase. The status of a test case goes from Planned, In work, to Completed.

    Project Settings

  3. Click PROJECT in menu.
  4. Click Settings. The list is about the various technical components:

    • Commander
    • Diagnostics
    • Engine
    • License
    • Special Engines
    • TBox
    • TCase from XL
    • TEx
    • TOSCAViewer
    • Tricentis Services
    • Wizard



    UI Tour

    As with other Windows UI apps such as Microsoft Word/Excel/Project, when each menu item is clicked, its ribbon appears.


    The blue icons at the top are for save, undo, redo. The save icon is iconic (of a removeable “discette” used during the 1990’s to store data). You can’t undo after Save. An Admin can revert a project to a previous version using change history.

    PROTIP: Turn on comments w ??? Turn on association with a Git revision.

    The left pane is for navigation, the middle page is the working pane.

    Window tabs (such as “test cases”) makes it easier to use the mouse among sections which are listed alphabetically within the left navigation pane but can be arranged to a lifecycle sequnece such as:


    1. Requirements (yellow) to specify requirements for your TestCases and to assign risk coverage for prioritizing test effort.

    2. Modules (orange) to create modules for use in TestCases. Modules contain technical information used to steer test objects.

    3. Configurations structure your test configuration parameters at one specific point in your repository.

    4. TestPlanning to plan software quality assurance (QA) activities across the application lifecycle.

    5. TestCasesDesign (red) to put test cases (functional flows) into a logical structure by creating a TestSheet to show all possible combinations of TestCases required to ensure full test coverage.

    6. TestCases (blue) ctrl+N, cntr+F, to create TestCases, which are made up of a series of TestSteps.

    7. Execution (green) to see the logs and results of standard or exploratory test runs which can be sped up with distributed execution.

    8. Issues to manage undesired behavior of the system under test. Create new issues that come up during test execution, or link existing issues to a TestCase log.

    9. BI-Testing

    10. Reporting (Addin) to create reports to document the status of your project.

    11. Test Data Management (not shown) to manage, use, and reuse your test data.

  5. Drag and drop each section tab to the above sequence.


    To expand text column size to fit, double-click on the gray bar between two column headings.

    Right-Click on Name. Select Column Chooser. Drag Description and drop on column heading.

    Keyboard shortcuts

    After highlighting an item …

    ctrl+T for a list. But remember to rename what is added.

    ctrl+. to add additional item.


  1. Identify the Requirements criteria which the system under test is expected to fulfill, then create a clear Requirement structure that reflects these criteria.

    1. open and login to the Web Shop
    2. order the product “Blue Jeans”
    3. check out and pay using a credit card
    4. verify the price of the order and that the correct shipping costs have been applied
    5. log out of the Web Shop and close Internet Explorer

    The weight is calculated from 2 to the power of (Frequency class + Damange class). So 2 to 4 + 4 = 2 to the power of 8 = 256.

    Each (business risk) Contribution % is based on the total of weights. This provides guidance on allocation of testing budget.

  2. Design a logical test structure to see what you need to cover Requirements. Use TestCase-Design to create combinations of possible TestCases.

    Right-click TestCases to create TestSheet,

    Right-click test sheet to create Instances

    Right-click Login to create Folder, Folder structure, Virtual Folder, Test configuration parmaeter (.), Class.

    Right-click an Attribute to Toggle Business Relevance by pressing Ctrl+F7 so its icon turns color. Name it Verification.

  3. Create Modules that contain the technical information Tricentis Tosca needs to steer the system under test. For steering, make an element uniquely identifiable in XScan:

    • Target’s own properties or Parent of subordinate controls
    • Anchor controls on the same page
    • In relation to an image on the page
    • Index (sequence of occurance of the same property on a web page)
    • SmartID ?

    Right-click on a Module’s attribute (that represent individual controls shown by the app) to Convert to ControlGroup with a name.

    Rename and save each module after identifying its controls.

  4. Create concrete TestCases folders out of your Modules. TestCases are a series of TestSteps that verify requirements specifications.

    A Workspace is a local copy of certain parts of a repository for a whole project.

    Right-click on a test case to select Run from Scratchbook.

    Each should have:

    • Precondition
    • (workflow steps) Order Product, Start Checkout to obtain a total price
    • Verification of prices
    • Confirmation
    • Verification of success
    • Postcondition

    TCP (Test Case Parameter) applies predefined values to various test cases for various object types (case sensitive naming), such as the browser used during testing.

    Build up a straight-through test case.

    Convert to a template. Build it up with data.

    Link the template to a test sheet.

    Drag Test case and drop in Requirements, Schema Name gets set.

    Which attribute goes to which value.

    TestCase Design contain instances.

  5. Configure tests. You can centrally manage test configuration parameters for your team.

    To scan, right-click:


    The scan pop-up dialog Advanced view:

  6. Prepare and perform the execution of your tests (see chapter “Execute tests”).

    Once you have executed your tests, Tricentis Tosca maps the test results with your Requirements. This gives you a good overview of

    • your testing status
    • the status of your system under test

    Create ExecutionList and call it “Regression”.

    Set result to “Passed” or “Failed”.

    To link Requirements, drag the whole Regression suite to drop in Requirements.

    Now you can right-click to “Jump to”.

    Execcution Test configuration can override plans, such as Browser.

TODO: ToscaDoctor using TQL to lint naming convention consistency to some rules.

  • No more than 15 items per level (see it all on one screen). Reorganize into folders containing clusters.

Interactive Testing

VIDEO: https://vimeo.com/336815189

  1. Setup a testing session
  2. Distribute manual test cases

    Each session includes information on testers, assignments, test progress, issues raised.


In Tosca, functions are written under {} and Parameters under [].

Action {Click} moves the cursor to the center of the link, triggering any mouse overs along the way.


ClickJUMP does not trigger mouse overs along the way. Alternately, a value “X” injects Javascript into the browser that clicks the element such that doesn’t move the mouse.

Avoid using buffer values, referenced by entry such as ctrl+T, Tbox set buffer, then {B[Email]} because buffers are only local and transitory. View, Show DoNothing such as “". F9 key. The B[Email] must be defined before steps that use it. Use it for reorder numbers that change. Instead use `CP` defined by TCP.

Generic test case: For values which can have multiple values (such as “News Stories” in the demo), define a Property named ExplicitName with True value, then replace the name of the Module with #1 for the first, #last for the last, or #{B[...]} to lookup in the Buffer.

For use with Generic controls: ResultCount is the number of controls which match a particular criteria within ActionMode “Buffer”. It’s not in a drop-down. Click the round blue circular down arrow to define fields to yield .ResultCount->StoryCount.

Create a “Hover every comment” tst case under “Click last story”. In property “Repetition” put value {B[StoryCount]}. Instead of #1, put #{REPETITION} to take action in Value {MOUSEOVER} for ActionMode Input.


Tricentis: A Tosca E2E Test Automation Example Aug 15, 2016 by Ominik Weissböck


Avoid of using static waits of a specific amount of time. Instead, use “wait on” event such as some text appearing (20 seconds by default set by TCP “SynchronizationTimeoutDuringWaitOn”). They could be additive.

Avoid copy and pasting parts of flows. Instead use Repetition tolders and/or ReusableTestStepBlocks.

To see what value is being viueled, temporarily put “.innertext=WRONG”.

Always define clean-up scenarios to clean up the test environment so that test steps after a step failure don’t create a cascade of several failed steps, which make troubleshooting more difficult.

Define recovery scenario for known responses such as setting a new password when the previous password expires (a common situation).

Analyze the time each step took to run (the time servers took to “think”) by extracting and analyzing results in the Scratchbook.

Dynamic Control

Choose properties that uniquely identify the ccontrol

Update the property of the control to pull the valuee from a Buffer.

Use “TBox Set Buffer” to set the Buffer to the desired control.

Take the desired using the module.

Excel (v12.1)

  1. In Modules, under Standard modules > TBox XEngines > Excel.

    #1 refers to the header row.

    $1 refers to the first data row (row 4 in Excel).

    References columns using #1 even though Excel uses A,B,C, etc.

Constraint ActionMode are considered before anything else.

KB0014621 on Excel


Tosca uses TBox ODBC connection by installing sqliteodbc_w64.exe (SQLite ODBC for Win64 Installation) from https://ch-werner.de/sqliteodbc/

Search “ODBC” and click “ODBC Data Sources (64-bit)” for Open ODBC Data sources with path: Control panel -> Administrative tools. Click “Run as administrator” for the “ODBC Data Source Administrator”. Click the “Drivers” tab to see SQLite. Click “User DSN” tab. Click Add. Use SQLite3.

Get SQLiteStudio 3.2.1 https://sqlitestudio.pl/index.rvt?act=download (Instead of clicking Add) Drag the database file to the white part on the left.

To verify a single cell value in a database: In TestCases: create Databases folder. Rename it “Database”. Create TestCase. Name it “Get count”. ctrl+T to get “TBox DB Expert module”. Expand Open Connection. DSN Value “Insurance”. For SQL Statement value, “select count(LicensePlateNuber) from TypeOfVehicle”. Expand Result Table.

select MileageYear from

Business Revelance to Attributes