Tosca Commander Objects

Tosca Commander - TestCases are created, executed and organized in Tosca Commander.

Tosca Commander is inspired by Microsoft Windows Explorer, which means that all items are mapped in a tree structure. We can open any no of windows and display a freely definable section of this tree structure.

If we select an item in the tree view. Tricentis Tosca displays the item details in the Details view.

TestCases - A TestCase consists of several TestSteps which determines the Test process.

TestSteps - TestSteps are processed in sequential order and each TestStep maps one page of the TricentisSample Application also known as the test object.

TestStepValues - We Specify your test data in the TestStepValues of the TestSteps. Tosca uses this test data during test execution, for instance when a specific text is written to an input field, or when a button is clicked.

Modules - Automated TestSteps are based on Modules.

Modules contain technical information which is used to identify and steer screen items. These items can be, for instance buttons or input fields. Tosca creates a ModuleAttribute for each item and saves this to the Module.

In Tosca, test data are separated from technical steering information. This way you can reuse Modules to create various TestSteps for any no of Testcases in order to test a variety of data.

ExecutionLists - We can create ExecutionLists to run our testcases and log the results of the test execution.

Object Hierarchy - Objects in Tosca Commander have a strict hierarchical structure. we must keep the object hierarchy when we copy or move Objects.

NOTE- We cannot copy TestCase Folders to TestStep folders or Module folders.

TOSCA Objects- 

Module - Represent the technical steering information

TestCases - Determine the test sequence and contain test data

ExecutionLists - Serve to plan and manage the test execution.

Tosca Commander 

Title Bar - The title bar in Tosca Commander shows the name of the currently open workspace. The title bar also includes the quick access toolbar which provides options such as Save, Undo etc. 

Menu (Ribbon) - The Menu is designed in the form of ribbons and consists of several tabs which allow you to access the corresponding Tosca Commander functions. These functions are either enabled or disabled, depending on the context you are working in.

If we switch between the windows of the various sections or selected objects within the sections, Tricentis Tosca opens an additional tab for this scetion that includes a dynamic menu. the dynamic menu shows relevant options for the selected section or object.

A Dynamic menu is available for the followings.

1. TestCases

2. Modules

3. Requirements

4. TestCaseDesign

5. Execution

6.Reporting

Within  the Execution section, a dynamic menu is also avialable for the subsections ExecutionLists and Exploratory Testing.

Status Bar - The Status bar shows the action that is currently performed by Tosca Commander.

Context Menu and Mini ToolBar -  In Tricentis Tosca you can process workspace objects via the context menu or the dynamic menu. The context menu provides options that are relevant for the respective object.

Open the context menu by right clicking on any object in the workspace.

TOSCA

1. What is Tosca
   
2. Tosca Versions History
   
3. Whats new in Tosca 16.0
   
4. FrameWorks
   
5. Advantages of Tosca
   
6. Disadvantages of TOSCA
   
7. TOSCA Commander
8. XScan
   
9. Module Types
   
10. Workspace Creation
11. Single User Workspace
    
12. Multi User Workspace
    
13. Subsets
    
14. Navigations
    
15. Naming Conventions
    
16. Repository Structure
    
17. Model-Based Test Automation
    
18. ActionModes
    
19. Spcify Values
20. Click Operations
    
21. Identify Controls In Tosca XScan
    
22. Identify controls by Properties
    
23. Identify Controls by Anchor
    
24. Identify controls by index
    
25. Identify controls by image
    
26. Scan tables
27. Test Data Management - TDM
    
28. Recovery Scenarios
    
29. Recovery Scenarios during execution
    
30. CleanUp Scenarios
    
31. CleanUp Scenarios during execution
    
32. Test Mandates in Execution
    
33. TCD, TDS and TDM
    
34. TBox Start Program
    
35. String Operations in TOSCA
    
36. Basic Windows Operations 
    
37. Test Events
    
38. Regular expressions
    
39. Tosca Distributed Execution -DEX
    
40. Tosca TEST Data Service (TDS)
    
41. Control Types in Tosca
    
42. TQL
    
43. How Distribution Execution works withAOS and withoutAOS
    
44. Anchor Controls
    
45. Tosca Engines 3.0
    

Automation Frameworks

 1. Linear Scripting:

Is nothing but 'Record and Playback', simplest among all other. Here tester can manually record each step like user navigation, input, verifying result. And then can play back recorded scripts as per requirement.

2. Modular Framework:

In this approach, scripts can be created and executed using reusable components. Here we can create small, independent scripts that represent modules, sections, and functions of the application-under-test. 

  

3. Library Architecture Framework:

It divides the application-under-test into procedures and functions in its place of scripts. This framework requires the creation of library files that represent modules, sections, and functions of the application-under-test. These library files are then called directly from the test case script. 

   

4. The Data-Driven Testing Framework :

Test case logic resides in Test Scripts, the Test Data is separated and kept outside the Test Scripts. Test Data is read from the external files (Excel Files, Text Files, CSV Files, ODBC Sources, DAO Objects, ADO Objects) and are loaded into the variables inside the Test Script. Navigation through the program, reading of the data files, and logging of test status and information are all coded in the test script.

5. The Keyword-Driven or Table-Driven Testing Framework :

As name suggests, Keyword is nothing but a code which represents some actions, say 'Register'. This framework requires the development of data tables and keywords, independent of the test automation tools used to execute them and the test script code that "drives" the application-under-test and the data. Keyword Driven Testing Framework is suitable for automation of small applications.

6. The Hybrid Test Automation Framework:

The most commonly implemented framework is a best combination of all the techniques. Hybrid Framework combines the best of Keyword Driven and Data Driven frameworks. Tests are fully scripted in a Hybrid Testing Framework thus increasing the automation effort. Hybrid Testing Framework also implements extensive error and unexpected windows handling. It is used for automation of medium to large applications with long shelf life. Above is a brief description about automation framework types. You can choose any framework as per your project requirement. Automation Framework is the practice of keeping all reusable, common components in one place constructing them as a platform to execute your automation scripts and all application specific data are passed as arguments to those functions.

WebTable Methods

 

ActivateCell	Double-clicks the specified cell in a table. Syntax- object.ActivateCell (Row, Column)
CaptureBitmap	Saves a screen capture of the object as a .png or .bmp image using the specified file name. Syntax-
Check	Checks whether the actual value of an item matches the expected value.
CheckProperty	Checks whether the actual value of the specified object property matches the specified expected value within the specified timeout.
ChildObjects	Returns the collection of child objects contained within the object.
GetAllROProperties	Returns the collection of properties and current values from the object in the application.
ClickCell	Emulates a click on the specified cell in a table.
ColumnCount	Retrieves the number of columns in the table.
DeselectColumn	Clears the selection of the specified column.
DeselectRow	Clears the selection of the specified row.
DeselectRowsRange	Clears the selection of the specified rows in the table.
ExtendColumn	Selects an additional column in the table.
ExtendRow	Selects an additional row in the table.
ExtendRowsRange	Adds the specified range of rows to the selected rows in the table.
FindAllRowsByCellContent	Retrieves all rows of all cells in the given column whose content matches the specified data.
FindRowByCellContent	Retrieves the first row of the cell in the given column whose content matches the specified data.
GetCellData	Returns the data contained in the specified cell.
GetCellDataEx	Returns a cell's content from a row with specific content in another cell.
GetCellLength	Retrieves the maximum length of the cell.
GetROProperty	Returns the current value of the description property from the object in the application.
GetTOProperties	Returns the collection of properties and values used to identify the object.
GetTOProperty	Returns the value of the specified description property from the test object description.
Highlight	Highlights the object in the application.
Input	Records an Input statement each time new or modified table cell data is sent to the SAP server.
IsCellEditable	Checks whether the cell is editable.
OpenPossibleEntries	Opens the list of possible entries for a table.
Output	Retrieves the current value of an item and stores it in a specified location.
PressSettingsButton	Presses the table setting button.
RefreshObject	Instructs UFT One to re-identify the object in the application the next time a step refers to this object.
RowCount	Returns the number of rows in the table.
SelectAllColumns	Selects all columns in the table.
SelectCell	Selects the specified cell in a table.
SelectColumn	Selects the specified column in the table.
SelectRow	Selects the specified row in the table.
SelectRowsRange	Selects the specified range of rows in the table.
SetCellData	Sets the cell contents with the specified data.
SetTOProperty	Sets the value of the specified description property in the test object description.
ToString	Returns a string that represents the test object.
ValidRow	Indicates whether or not the specified row is a valid row for the table.
WaitProperty	Waits until the specified object property achieves the specified value or exceeds the specified timeout before continuing to the next step.

Selenium WebDriver Commands

Selenium WebDriver commands can be classified as Get commands, Navigation commands, WebElement commands, Action commands, and Result commands.

Get Commands - Get commands are the most commonly used commands to perform the basic operations of WebDriver such as opening a browser, performing a few tasks, and then closing the browser.

Syntax: get(String arg) : void

The get() method takes a string URL as a parameter and returns nothing.

Syntax:

1

  driver.get(https://www.google.com);

Example - 

driver.get("https://www.google.com"); 

// Or It can be also written as 

String URL = "https://www.scientecheasy.com"; 

driver.get(URL);

Get Current URL -   The getCurrentURL() method takes nothing as a parameter and returns URL of the web page currently loaded in the browser.

getCurrentUrl() : String

Syntax:
driver.getCurrentUrl();

Example - 

driver.getCurrentUrl(); 

// The above code can be also written as 

String currentUrl = driver.getCurrentUrl(); 

// Since the return type of getCurrentUrl() method is String. So, we will store it using variable currentUrl with String data type.

Get Title Command - The getTitle() method takes nothing as a parameter and returns the page title of the currently loaded web page. If the web page has no title, it will return a null String.

getTitle() : String

Syntax:
driver.getTitle();

Example - 

driver.getTitle(); 

// The above code can also be written as 

String title = driver.getTitle(); // Return type of getTitle is String.

Get Page Source Command-  The getPageSource() method accepts nothing as a parameter and returns the source code of the current web page. This method is used to get the page source code of the currently loaded web page.

Syntax:

driver.getPageSource();

Example - 

driver.getPageSource(); 

// Or 

String pageSource = driver.getPageSource();

// Since return type of the this method is String. Therefore, the output must be stored in a variable with datatype String.

Get Text Command -   The getText() method accepts nothing as a parameter and returns a string value. This method is used to retrieve the inner text of the specified element.

getText() : String

Syntax:

driver.findElement(By.locatorName(“Specified Element”)).getText();

Example - 

String text = driver.findElement(By.id("India")).getText(); // id is name of locator. India is a specified element. 

System.out.println(text); 

// The above code can also be written as 

WebElement element=driver.findElement(By.id("India")); 

String text=element.getText(); // Return type of getText method is String. 

System.out.println("Inner Text: " +text);

Get Tag Name Command- The getTagName() method takes nothing as a parameter and returns a String value. This method is used to get the tagName of the WebElement returned by the findElement(By) method.

getTagName() : String

Syntax:
element.getTagName(); // Here. element is a variable whose return type is WebElement.

Example -

String tagName = driver.findElement(By.id("DownloadButton")).getTagName(); 

// or 

WebElement element = driver.findElement(By.id("DownloadButton")); 

String tagName = element.getTagName(); 

System.out.println(tagName);

Get CSS Value Command- The getCssValue() method accepts nothing as a parameter and returns a String value. This method is used to fetch the value of the CSS property of the given web element when it is invoked.

getCssValue() : String

Syntax:
element.getCssValue();

Get Attribute Command -  The getAttribute() method takes the String as a parameter and returns a String value. It is used to fetch or get the value of the attribute of the WebElement.

getAttribute(String Name) : String

Syntax:
element.getAttribute();

Example - 

WebElement element = driver.findElement(By.id("DownloadButton")); 

String attributeValue = element.getAttribute("id"); //This will return "DownloadButton". 

System.out.println(attributeValue);

Get Size Command-  The getSize() method does not accept any parameter but returns the size of the element on the page. This method is used to fetch the width and height of the rendered element.

getSize() : int

Syntax:
element.getSize();

Example - 

WebElement element = driver.findElement(By.id("DownloadButton")); 

Dimension elementSize = element.getSize(); 

System.out.println(“Height :” + elementSize.height + ”Width : "+ elementSize.width);

Close Command - The close method takes nothing as a parameter and returns nothing. This method is used to close only the browser window that web driver is currently controlling.

close() : void

Syntax:
driver.close();

Quit Command - The quit() method accepts nothing as a parameter and returns nothing. This method is used to close all windows opened by WebDriver.

quit() : void

Syntax:
driver.quit();