This document provides instructions for completing a tutorial in Tosca Commander. It begins by introducing Tosca Commander and how to start it. It then discusses the key objects in Tosca like Modules, Test Cases, and Execution Lists. The document explains how to create a workspace and navigate Tosca Commander. It also introduces the sample application that will be used for testing. The remaining chapters will guide the user through creating Modules, Test Cases, and executing the Test Cases on the sample application.
1. The document provides instructions for installing Tomcat and setting up a basic web application with servlets on a Windows system. It describes downloading and installing Java, setting the JAVA_HOME environment variable, downloading and installing Tomcat, and creating a simple "HelloWorld" servlet application.
2. It then gives examples of additional servlet programming concepts like sending request parameters, generating HTML tables, using sessions, servlet forwarding, and accessing databases with JDBC.
3. For each example, it provides the HTML, Java code, and instructions for compiling and running the servlets on the Tomcat server.
It covers all the basics of MATLAB required for beginners. After going through these slides, anyone can write a MATLAB program and apply it to his field of interest.
I am Kefa J. I am a Database Management Homework Expert at databasehomeworkhelp.com. I hold a Ph.D. in Programming, Princeton University, USA. I have been helping students with their homework for the past 12 years. I solve homework related to Database Management.
Visit databasehomeworkhelp.com or email info@databasehomeworkhelp.com. You can also call on +1 678 648 4277 for any assistance with Database Management Homework.
This document provides instructions for reformatting a document delivered in 8.5x11 US letter format to print on A4 paper. It outlines four simple steps: 1) Open the document in Word and select A4 paper size, 2) Update the second page, 3) Reindex the last page, and 4) Save under a new name for convenience. The document also introduces automated testing and the TestComplete tool for creating tests.
This document provides a tutorial for using Ranorex to test the GUI of a SimpleCalculator application. It discusses:
1. Installing and setting up Ranorex, which allows simulating user interactions for GUI testing.
2. Adding a GUITester class to an existing SimpleCalculator project and referencing the Ranorex library.
3. Writing tests that use Ranorex methods to control the mouse, interact with calculator controls, and assert the result is correct.
4. Running the GUI tests using the NUnit test runner to automatically simulate user interactions and verify functionality.
This document provides instructions and tutorials for a lab on Visual Basic and spreadsheet programming basics. The lab consists of three tutorials that students should complete during the lab session or on their own time. The tutorials cover topics like creating macros, recording macros, modules and procedures, objects and collections in VBA, and the Range and Cells objects. Students are expected to work through examples and tasks in each tutorial. Their understanding of the material will be assessed on an upcoming Excel exam.
The document contains interview questions and answers related to sections, control identification, modules, actions, parameters, and other concepts in Tosca automation testing. Key points include the different section types in Tosca, methods for identifying controls, types of modules, actions like verify and buffer, parameters like TCP and business parameters, and concepts like synchronization, libraries, and recovery scenarios.
The document introduces the SessionCreator tool, which allows users to create test sessions, conduct reviews, and access reports. It can be used as an add-on to the Session-Based Test Management tool or as a standalone program. The SessionCreator guides users through a wizard to set up test sessions, select test areas, record session details, and save results. It also provides a review page to facilitate session debriefs and a report page with test data summaries.
1. The document provides instructions for installing Tomcat and setting up a basic web application with servlets on a Windows system. It describes downloading and installing Java, setting the JAVA_HOME environment variable, downloading and installing Tomcat, and creating a simple "HelloWorld" servlet application.
2. It then gives examples of additional servlet programming concepts like sending request parameters, generating HTML tables, using sessions, servlet forwarding, and accessing databases with JDBC.
3. For each example, it provides the HTML, Java code, and instructions for compiling and running the servlets on the Tomcat server.
It covers all the basics of MATLAB required for beginners. After going through these slides, anyone can write a MATLAB program and apply it to his field of interest.
I am Kefa J. I am a Database Management Homework Expert at databasehomeworkhelp.com. I hold a Ph.D. in Programming, Princeton University, USA. I have been helping students with their homework for the past 12 years. I solve homework related to Database Management.
Visit databasehomeworkhelp.com or email info@databasehomeworkhelp.com. You can also call on +1 678 648 4277 for any assistance with Database Management Homework.
This document provides instructions for reformatting a document delivered in 8.5x11 US letter format to print on A4 paper. It outlines four simple steps: 1) Open the document in Word and select A4 paper size, 2) Update the second page, 3) Reindex the last page, and 4) Save under a new name for convenience. The document also introduces automated testing and the TestComplete tool for creating tests.
This document provides a tutorial for using Ranorex to test the GUI of a SimpleCalculator application. It discusses:
1. Installing and setting up Ranorex, which allows simulating user interactions for GUI testing.
2. Adding a GUITester class to an existing SimpleCalculator project and referencing the Ranorex library.
3. Writing tests that use Ranorex methods to control the mouse, interact with calculator controls, and assert the result is correct.
4. Running the GUI tests using the NUnit test runner to automatically simulate user interactions and verify functionality.
This document provides instructions and tutorials for a lab on Visual Basic and spreadsheet programming basics. The lab consists of three tutorials that students should complete during the lab session or on their own time. The tutorials cover topics like creating macros, recording macros, modules and procedures, objects and collections in VBA, and the Range and Cells objects. Students are expected to work through examples and tasks in each tutorial. Their understanding of the material will be assessed on an upcoming Excel exam.
The document contains interview questions and answers related to sections, control identification, modules, actions, parameters, and other concepts in Tosca automation testing. Key points include the different section types in Tosca, methods for identifying controls, types of modules, actions like verify and buffer, parameters like TCP and business parameters, and concepts like synchronization, libraries, and recovery scenarios.
The document introduces the SessionCreator tool, which allows users to create test sessions, conduct reviews, and access reports. It can be used as an add-on to the Session-Based Test Management tool or as a standalone program. The SessionCreator guides users through a wizard to set up test sessions, select test areas, record session details, and save results. It also provides a review page to facilitate session debriefs and a report page with test data summaries.
This tutorial demonstrates how to implement a mechanical part in Vulcan by:
1. Creating two layers ("aux" and "profile") to organize the geometry creation.
2. Using the "aux" layer for auxiliary lines and the "profile" layer for lines defining the part profile.
3. Generating a volume defined by the profile lines.
4. Generating a mesh of the part to enable meshing analysis.
This document provides an overview of a webinar on using macros to customize outputs from VisibleThread Docs. The webinar covers how to record macros in Excel to automate tasks, add custom macros to the VT macro template, and test macros. It also discusses writing macros using VBA code for more advanced customization. The webinar includes examples of macros that could format columns, combine content from different volumes, and conditionally highlight text.
This document contains 50 tips for improving productivity in Microsoft Excel. Some key tips include:
1. Users can easily post data to the web using Excel's wizard-driven Save As HTML feature.
2. Excel can open web pages directly from their URL, saving retyping if data needs to be analyzed from a website.
3. The Detect and Repair command line tool checks and fixes problems with Excel files, DLLs, and registry settings.
This document provides information and instructions for various Excel functions and features, including:
- Formatting cells using merged cells and wrapping text in merged cells.
- Generating lists of filenames and sheet names using named formulas and functions.
- Customizing the Quick Access toolbar and Ribbon.
- Understanding protected view, auto recover, and read-only file formats for sharing workbooks.
- Locating and unmerging all merged cells in a worksheet.
This document provides information and instructions for various Excel functions and features, including:
- Formatting cells using merged cells and wrapping text in merged cells.
- Generating lists of filenames and sheet names using named formulas and functions.
- Customizing the Quick Access toolbar and Ribbon.
- Understanding protected view, auto recover, and the different Excel file formats.
- Finding and unmerging all merged cells in a worksheet.
You are tasked with gaining privileged access to a Windows 2008 server through a capture-the-flag event. You first use Metasploit to exploit vulnerable MS SQL services to get an unprivileged shell. Then, you use the exploit suggester module to find exploits for privilege escalation, using the ms16_014_wmi_recv_notif exploit to achieve a privileged shell. Finally, you perform an action like deleting important files to cause an information security breach on the target system.
BLCN532 Lab 1Set up your development environmentV2.0.docxmoirarandell
BLCN532 Lab 1
Set up your development environment
V2.0
Introduction
This course introduces students to blockchain development for enterprise environments. Before you can develop software applications, you need to ensue your development environment is in place. That means you’ll need all the tools and infrastructure installed and configured to support enterprise blockchain software development projects.
In this lab you’ll set up your own Hyperledger Fabric development environment and install the course software from the textbook. When you finish this lab, you’ll have a working development environment and will be ready to start running and modifying blockchain applications.
The instructions in your textbook are for Mac and Linux computers.
However
, there is no guarantee that your installation of MacOS or Linux is completely compatible with the environment in which the commands from the textbook work properly. For that reason, I
STRONGLY SUGGEST
that you acquire an Ubuntu 16.04 Virtual Machine (VM) for your labs. Using an Ubuntu 16.04 VM will make the labs far easier to complete.
The instructions in this course’s labs assume that your computer runs the Windows operating system. If you run MacOS or Linux, you can get
Vagrant
and
VirtualBox
for those operating systems and follow the gist of the “Initial setup for Windows computers”.
Lab Deliverables:
To complete this lab, you must create a
Lab Report file
and submit the file in iLearn. The Lab Report file must be a Microsoft Word format (.docx), and have the filename with the following format:
BLCN532_SECTION_STUDENTID_LASTNAME_FIRSTNAME_Lab01.docx
· SECTION is the section number of your current course (2 digits)
· STUDENTID is your student ID number (with leading zeros)
· LASTNAME is your last name, FIRSTNAME is your first name
To get started, create a Microsoft Word document (.docx) with the correct filename for this lab. You’ll be asked to enter text and paste screenshots into the lab report file.
NOTE: All screenshots MUST be readable. Use the Ubuntu Screen Capture utility (see the lab video.) Make sure that you label each screenshot (i.e. Step 2.1.3) and provide screenshots in order. For commands that produce lots of output, I only want to see the last full screen when the command finishes. Provide FULL screenshots, NOT cropped images.
SECTION 1: Initial setup for Windows computers (Chapter 3)
Step 1.1: Install Oracle Virtualbox (Windows, Linux, MacOS)
Oracle Virtualbox is an open source virtualization environment that allows you to run multiple virtual machines and containers on a single personal computer. Virtualbox is free and it is easy to install.
In your favorite web browser, navigate to:
https://www.virtualbox.org/
and click the “Download Virtualbox” button. Click the “Windows hosts” link to download the main installation executable. You should also click the “All supported platforms” under the “Extension Pack” heading to download extra software supp.
The document provides an overview of Lab 1 for ECEN 474/704. The objectives are to learn Linux commands, Cadence basics, and MOS transistor characterization. Students will create an inverter schematic in Cadence, simulate it, and measure transistor model parameters like threshold voltage. The document reviews transistor operation and SPICE models. It provides instructions for starting Cadence, creating a library and cell, building an inverter schematic, setting up a DC simulation, and interpreting output plots.
This document provides an overview of basic Python skills needed to complete labs and problem sets, including logging into a server, using the Python shell and IDLE integrated development environment, running Python scripts locally, and basic Python operations like arithmetic, variables, lists, tuples, strings, and modules. It covers starting the Python interpreter, using xterms and logging into a server, the Python shell and IDLE, running Python scripts from the command line or within IDLE, and demonstrates basic Python concepts like arithmetic, variables, lists, tuples, strings, and modules through examples.
This document provides an overview of various Excel 2013 features, including:
1) Formatting options such as merging and wrapping text in cells, locating and unmerging merged cells.
2) Using functions, formulas, and named ranges to generate lists of file names and sheet names.
3) Customizing the Quick Access toolbar, Ribbon, and other interface elements. Saving files in different formats like PDF.
4) Understanding features like Protected View, AutoRecover, and using Excel in a web browser.
Generic Repository Pattern in MVC3 Application with Entity FrameworkAkhil Mittal
This document discusses implementing a generic repository pattern and unit of work pattern in an MVC application using Entity Framework. It begins by introducing the concepts of a generic repository and unit of work. It then shows how to create a generic repository class that can be used for any entity. A unit of work class is created to manage transactions and repositories. Properties on the unit of work class provide access to repositories without having to create separate classes. CRUD operations on entities are demonstrated using the generic repository through the unit of work. This completes the tutorial on implementing these patterns to reduce redundant code and complexity in an MVC application.
This document provides instructions for a practice in an Oracle Database 11g: PL/SQL Fundamentals course. It includes:
1. Instructions on setting up the workspace and creating a database connection in SQL Developer.
2. A multi-step practice assignment involving browsing database tables, writing SQL queries, and creating PL/SQL blocks with variables, comments, and logic.
3. Hints that the solutions to practices can be found in an appendix and that students should save their work in a provided labs folder.
( 13 ) Office 2007 Coding With Excel And Excel ServicesLiquidHub
This document provides instructions for a lab on coding with Excel and Excel Services. It involves publishing an Excel workbook to a document library as a trusted file location, then developing a C# console application that uses the Excel Services Web Service to call the workbook, pass in parameters, retrieve calculation results, and display them. The lab demonstrates how to incorporate spreadsheet logic into applications while protecting proprietary information on the server. Completing the lab takes an estimated 60 minutes and involves publishing the workbook, setting up the trusted location, adding a web reference, coding the application to open the workbook, set cell values, calculate, get results and close the session, building the project, and running the application with sample inputs to test it.
(150324) Everything you ever wanted to know about Studio!Paul Filkin
The powerpoint presented as part of the workshop held in Warsaw in March 2015 during the Translation & Localisation Conference 2015.
I enhanced it a little with some a few extra slides covering some of the things we talked about in addition to the questions submitted beforehand.
This document provides instructions for creating a simple test in TestComplete. It describes adding the sample Orders application to the list of tested applications, planning a test to add a new order, recording user actions to perform that test, analyzing the recorded test, running the test, and analyzing the test results. The goal is to create an automated test that emulates user actions in the Orders application and verifies that a new order was added correctly.
( 13 ) Office 2007 Coding With Excel And Excel ServicesLiquidHub
This document describes a lab on coding with Excel and Excel Services. It involves publishing an Excel workbook to a document library as a trusted file location, then developing a C# console application that uses the Excel Services web service to pass input values to the workbook, run calculations on the server, and return output values. The lab demonstrates how to incorporate spreadsheet logic into applications while protecting proprietary information on the server. Estimated completion time is 60 minutes.
Laporan Praktikum Keamanan Siber - Tugas 3 - Kelas C - Kelompok 3.pdfIGedeArieYogantaraSu
This document provides instructions for a lab on working with text files in the command line interface (CLI) of a Linux system. It covers using both graphical and command line text editors to open, modify, and save text configuration files. Specifically, it introduces the SciTE graphical text editor and nano command line text editor. It also explains that configuration files for applications are typically found in a user's home directory, while system-wide configuration files are located in the /etc directory.
This document provides an introduction to an advanced Microsoft Excel lesson. It discusses learning advanced customization and formatting features to allow for easier data manipulation and organization. The objectives covered include learning how to customize the Excel interface, use advanced formatting techniques, reference across sheets, use advanced formulas and data ranges, and apply data validation. The lesson then covers customizing the ribbon interface and status bar, navigating between windows and using panes, and referencing cells across different sheets.
Contents
COSC 2436 – LAB4
TITLE .............................................................................................................................................................. 1 TIME TO COMPLETE ...................................................................................................................................... 1 COURSE OBJECTIVES – LEARNING OUTCOME .............................................................................................. 1 LAB OBJECTIVES ............................................................................................................................................ 2 SKILLS REQUIRED........................................................................................................................................... 2 HOW TO DO EACH PART ............................................................................................................................... 2 REQUIREMENT .............................................................................................................................................. 3
LAB4 PART1 ............................................................................................................................................... 3
LAB4 PART2 ............................................................................................................................................... 4 HOW TO TURN IN THE LAB ........................................................................................................................... 6 HOW TO GRADE THE LAB.............................................................................................................................. 6
Note: in the instruction of the lab change “yourLastName” to your last name. In the example, change Smith to your last name, change James Smith to your full name, change Mary Lane to the name that users type in from the keyboard (if these words are in this instruction)
TITLE
Restricted Data Structure: Stack and Queue -Evaluating the infixed Math expression
TIME TO COMPLETE
Two week
COURSE OBJECTIVES
–
LEARNING OUTCOME
[LO1]
Provide UML class diagram and the code of data type classes
Provide the pseudo-code or flowchart based on the requirement of a project before writing the code of the driver class. Also, can access data members of data type classes
Describe and implement the inheritance relationship between super class and child classes.
Can use abstract classes or interface and apply polymorphism to the real life problem project
[LO3]
Describe and implement operations of Stack and Queue structures. Using Stack/Queue to the real life problem project
LAB OBJECTIVES
-Complete the lab on time (Time Management) -Can write the pseudo-code
-Can provide UML of data type class
-Can write comments in the program
-Can write the code of data type classes including data members, no-argument constructor, parameter constructors, mutator methods, ass.
Advanced Computer Forensics
Windows EnCase Forensics Lab
Due date: Please submit your work to Windows EnCase Lab dropbox by July 2nd, 2013.
Lab Setup for using RLES vCloud
This lab is designed to function on the RLES vCloud. The interface is available by navigating to https://rlesvcloud.rit.edu/cloud/org/NAT. If you did the Linux forensics lab on RLES vCloud, you should have created a vApp with the Linux VMware image. If you did not use the RLES vCloud for your first lab, please follow the instruction described in the Linux Forensics Lab to create a vApp. Now, you will add the vApp template, Windows 7 w/FTK 7 EnCase image, from the Public Catalogs to the same vApp following the instruction of Add Virtual Machines to a vApp (Page 8 in RLES vCloud User Guide) with the following setting:
· Set network to be Net_Network
· Select DHCP to create an IP address (when you use DHCP, fencing option is NOT necessary.)
Note: If you get an error when trying to start a vApp (or a VM within a vApp), try these steps:
1. Open up your vApp and click on the Virtual Machines tab. Right-click your VM and choose "Properties".
2. Click on the Hardware tab. At the bottom of the page, click on the MAC address and choose "Reset".
3. Click OK. When it asks if you want to enable guest customization, click No.
4. Give it a minute to update your VM, then try starting it.
Power on the Windows Virtual machine and login to the system with:
Username: Student
Password: student
EnCase 7 is installed on the virtual machine. When you start the EnCase application, you should see “EnCase Forensic (not Acquisition)” on the top of the application.
EnCase 7 Tutorial
· The EnCase Forensics V7 User Guide posted in myCourses under Hands-on Labs.
· EnCase 7 Essentials webinar series at http://www.encaseondemand.com/EnCasev7Essentials/tabid/2617/index.aspx
The following image files will be used for this lab and they are located in the local drive E:\
1) WinLabRaw.img – Raw Image from dd
2) WinLabEnCase.E01 -- EnCase evidence file
Note: “WinLabEnCase Image” in this documentation = “Lab5 image” in your EnCase image.
PART I: Familiar with EnCase
Exercise 1: Starting a New Case
Launch EnCase for Windows – make sure that you are in the EnCase forensics mode (on the top of the software, you should see EnCase Forensic Training, NOT acquisition mode.)
Click the “New Case” button under CASE FILE to begin a new case.
Use the #1 Basic Template and name the case “Case 1”
Record the defaults that EnCase gives you for its folders. It is safe to use these defaults in our experiments.
Add a Raw Image to the exist case
You can add a raw disk image, for example, the dd image, to your case.
Click EVIDENCE > Add Evidence, then click Add Raw Image
Enter “WinLabRaw Image” in the “Name” field.
Under “Image Type” choose “Disk” and click “OK”.
Under Component Files, click New, locate and select the “WinLabRaw.img” file from E:\
The image will now be added to your case. Double clic.
This tutorial demonstrates how to implement a mechanical part in Vulcan by:
1. Creating two layers ("aux" and "profile") to organize the geometry creation.
2. Using the "aux" layer for auxiliary lines and the "profile" layer for lines defining the part profile.
3. Generating a volume defined by the profile lines.
4. Generating a mesh of the part to enable meshing analysis.
This document provides an overview of a webinar on using macros to customize outputs from VisibleThread Docs. The webinar covers how to record macros in Excel to automate tasks, add custom macros to the VT macro template, and test macros. It also discusses writing macros using VBA code for more advanced customization. The webinar includes examples of macros that could format columns, combine content from different volumes, and conditionally highlight text.
This document contains 50 tips for improving productivity in Microsoft Excel. Some key tips include:
1. Users can easily post data to the web using Excel's wizard-driven Save As HTML feature.
2. Excel can open web pages directly from their URL, saving retyping if data needs to be analyzed from a website.
3. The Detect and Repair command line tool checks and fixes problems with Excel files, DLLs, and registry settings.
This document provides information and instructions for various Excel functions and features, including:
- Formatting cells using merged cells and wrapping text in merged cells.
- Generating lists of filenames and sheet names using named formulas and functions.
- Customizing the Quick Access toolbar and Ribbon.
- Understanding protected view, auto recover, and read-only file formats for sharing workbooks.
- Locating and unmerging all merged cells in a worksheet.
This document provides information and instructions for various Excel functions and features, including:
- Formatting cells using merged cells and wrapping text in merged cells.
- Generating lists of filenames and sheet names using named formulas and functions.
- Customizing the Quick Access toolbar and Ribbon.
- Understanding protected view, auto recover, and the different Excel file formats.
- Finding and unmerging all merged cells in a worksheet.
You are tasked with gaining privileged access to a Windows 2008 server through a capture-the-flag event. You first use Metasploit to exploit vulnerable MS SQL services to get an unprivileged shell. Then, you use the exploit suggester module to find exploits for privilege escalation, using the ms16_014_wmi_recv_notif exploit to achieve a privileged shell. Finally, you perform an action like deleting important files to cause an information security breach on the target system.
BLCN532 Lab 1Set up your development environmentV2.0.docxmoirarandell
BLCN532 Lab 1
Set up your development environment
V2.0
Introduction
This course introduces students to blockchain development for enterprise environments. Before you can develop software applications, you need to ensue your development environment is in place. That means you’ll need all the tools and infrastructure installed and configured to support enterprise blockchain software development projects.
In this lab you’ll set up your own Hyperledger Fabric development environment and install the course software from the textbook. When you finish this lab, you’ll have a working development environment and will be ready to start running and modifying blockchain applications.
The instructions in your textbook are for Mac and Linux computers.
However
, there is no guarantee that your installation of MacOS or Linux is completely compatible with the environment in which the commands from the textbook work properly. For that reason, I
STRONGLY SUGGEST
that you acquire an Ubuntu 16.04 Virtual Machine (VM) for your labs. Using an Ubuntu 16.04 VM will make the labs far easier to complete.
The instructions in this course’s labs assume that your computer runs the Windows operating system. If you run MacOS or Linux, you can get
Vagrant
and
VirtualBox
for those operating systems and follow the gist of the “Initial setup for Windows computers”.
Lab Deliverables:
To complete this lab, you must create a
Lab Report file
and submit the file in iLearn. The Lab Report file must be a Microsoft Word format (.docx), and have the filename with the following format:
BLCN532_SECTION_STUDENTID_LASTNAME_FIRSTNAME_Lab01.docx
· SECTION is the section number of your current course (2 digits)
· STUDENTID is your student ID number (with leading zeros)
· LASTNAME is your last name, FIRSTNAME is your first name
To get started, create a Microsoft Word document (.docx) with the correct filename for this lab. You’ll be asked to enter text and paste screenshots into the lab report file.
NOTE: All screenshots MUST be readable. Use the Ubuntu Screen Capture utility (see the lab video.) Make sure that you label each screenshot (i.e. Step 2.1.3) and provide screenshots in order. For commands that produce lots of output, I only want to see the last full screen when the command finishes. Provide FULL screenshots, NOT cropped images.
SECTION 1: Initial setup for Windows computers (Chapter 3)
Step 1.1: Install Oracle Virtualbox (Windows, Linux, MacOS)
Oracle Virtualbox is an open source virtualization environment that allows you to run multiple virtual machines and containers on a single personal computer. Virtualbox is free and it is easy to install.
In your favorite web browser, navigate to:
https://www.virtualbox.org/
and click the “Download Virtualbox” button. Click the “Windows hosts” link to download the main installation executable. You should also click the “All supported platforms” under the “Extension Pack” heading to download extra software supp.
The document provides an overview of Lab 1 for ECEN 474/704. The objectives are to learn Linux commands, Cadence basics, and MOS transistor characterization. Students will create an inverter schematic in Cadence, simulate it, and measure transistor model parameters like threshold voltage. The document reviews transistor operation and SPICE models. It provides instructions for starting Cadence, creating a library and cell, building an inverter schematic, setting up a DC simulation, and interpreting output plots.
This document provides an overview of basic Python skills needed to complete labs and problem sets, including logging into a server, using the Python shell and IDLE integrated development environment, running Python scripts locally, and basic Python operations like arithmetic, variables, lists, tuples, strings, and modules. It covers starting the Python interpreter, using xterms and logging into a server, the Python shell and IDLE, running Python scripts from the command line or within IDLE, and demonstrates basic Python concepts like arithmetic, variables, lists, tuples, strings, and modules through examples.
This document provides an overview of various Excel 2013 features, including:
1) Formatting options such as merging and wrapping text in cells, locating and unmerging merged cells.
2) Using functions, formulas, and named ranges to generate lists of file names and sheet names.
3) Customizing the Quick Access toolbar, Ribbon, and other interface elements. Saving files in different formats like PDF.
4) Understanding features like Protected View, AutoRecover, and using Excel in a web browser.
Generic Repository Pattern in MVC3 Application with Entity FrameworkAkhil Mittal
This document discusses implementing a generic repository pattern and unit of work pattern in an MVC application using Entity Framework. It begins by introducing the concepts of a generic repository and unit of work. It then shows how to create a generic repository class that can be used for any entity. A unit of work class is created to manage transactions and repositories. Properties on the unit of work class provide access to repositories without having to create separate classes. CRUD operations on entities are demonstrated using the generic repository through the unit of work. This completes the tutorial on implementing these patterns to reduce redundant code and complexity in an MVC application.
This document provides instructions for a practice in an Oracle Database 11g: PL/SQL Fundamentals course. It includes:
1. Instructions on setting up the workspace and creating a database connection in SQL Developer.
2. A multi-step practice assignment involving browsing database tables, writing SQL queries, and creating PL/SQL blocks with variables, comments, and logic.
3. Hints that the solutions to practices can be found in an appendix and that students should save their work in a provided labs folder.
( 13 ) Office 2007 Coding With Excel And Excel ServicesLiquidHub
This document provides instructions for a lab on coding with Excel and Excel Services. It involves publishing an Excel workbook to a document library as a trusted file location, then developing a C# console application that uses the Excel Services Web Service to call the workbook, pass in parameters, retrieve calculation results, and display them. The lab demonstrates how to incorporate spreadsheet logic into applications while protecting proprietary information on the server. Completing the lab takes an estimated 60 minutes and involves publishing the workbook, setting up the trusted location, adding a web reference, coding the application to open the workbook, set cell values, calculate, get results and close the session, building the project, and running the application with sample inputs to test it.
(150324) Everything you ever wanted to know about Studio!Paul Filkin
The powerpoint presented as part of the workshop held in Warsaw in March 2015 during the Translation & Localisation Conference 2015.
I enhanced it a little with some a few extra slides covering some of the things we talked about in addition to the questions submitted beforehand.
This document provides instructions for creating a simple test in TestComplete. It describes adding the sample Orders application to the list of tested applications, planning a test to add a new order, recording user actions to perform that test, analyzing the recorded test, running the test, and analyzing the test results. The goal is to create an automated test that emulates user actions in the Orders application and verifies that a new order was added correctly.
( 13 ) Office 2007 Coding With Excel And Excel ServicesLiquidHub
This document describes a lab on coding with Excel and Excel Services. It involves publishing an Excel workbook to a document library as a trusted file location, then developing a C# console application that uses the Excel Services web service to pass input values to the workbook, run calculations on the server, and return output values. The lab demonstrates how to incorporate spreadsheet logic into applications while protecting proprietary information on the server. Estimated completion time is 60 minutes.
Laporan Praktikum Keamanan Siber - Tugas 3 - Kelas C - Kelompok 3.pdfIGedeArieYogantaraSu
This document provides instructions for a lab on working with text files in the command line interface (CLI) of a Linux system. It covers using both graphical and command line text editors to open, modify, and save text configuration files. Specifically, it introduces the SciTE graphical text editor and nano command line text editor. It also explains that configuration files for applications are typically found in a user's home directory, while system-wide configuration files are located in the /etc directory.
This document provides an introduction to an advanced Microsoft Excel lesson. It discusses learning advanced customization and formatting features to allow for easier data manipulation and organization. The objectives covered include learning how to customize the Excel interface, use advanced formatting techniques, reference across sheets, use advanced formulas and data ranges, and apply data validation. The lesson then covers customizing the ribbon interface and status bar, navigating between windows and using panes, and referencing cells across different sheets.
Contents
COSC 2436 – LAB4
TITLE .............................................................................................................................................................. 1 TIME TO COMPLETE ...................................................................................................................................... 1 COURSE OBJECTIVES – LEARNING OUTCOME .............................................................................................. 1 LAB OBJECTIVES ............................................................................................................................................ 2 SKILLS REQUIRED........................................................................................................................................... 2 HOW TO DO EACH PART ............................................................................................................................... 2 REQUIREMENT .............................................................................................................................................. 3
LAB4 PART1 ............................................................................................................................................... 3
LAB4 PART2 ............................................................................................................................................... 4 HOW TO TURN IN THE LAB ........................................................................................................................... 6 HOW TO GRADE THE LAB.............................................................................................................................. 6
Note: in the instruction of the lab change “yourLastName” to your last name. In the example, change Smith to your last name, change James Smith to your full name, change Mary Lane to the name that users type in from the keyboard (if these words are in this instruction)
TITLE
Restricted Data Structure: Stack and Queue -Evaluating the infixed Math expression
TIME TO COMPLETE
Two week
COURSE OBJECTIVES
–
LEARNING OUTCOME
[LO1]
Provide UML class diagram and the code of data type classes
Provide the pseudo-code or flowchart based on the requirement of a project before writing the code of the driver class. Also, can access data members of data type classes
Describe and implement the inheritance relationship between super class and child classes.
Can use abstract classes or interface and apply polymorphism to the real life problem project
[LO3]
Describe and implement operations of Stack and Queue structures. Using Stack/Queue to the real life problem project
LAB OBJECTIVES
-Complete the lab on time (Time Management) -Can write the pseudo-code
-Can provide UML of data type class
-Can write comments in the program
-Can write the code of data type classes including data members, no-argument constructor, parameter constructors, mutator methods, ass.
Advanced Computer Forensics
Windows EnCase Forensics Lab
Due date: Please submit your work to Windows EnCase Lab dropbox by July 2nd, 2013.
Lab Setup for using RLES vCloud
This lab is designed to function on the RLES vCloud. The interface is available by navigating to https://rlesvcloud.rit.edu/cloud/org/NAT. If you did the Linux forensics lab on RLES vCloud, you should have created a vApp with the Linux VMware image. If you did not use the RLES vCloud for your first lab, please follow the instruction described in the Linux Forensics Lab to create a vApp. Now, you will add the vApp template, Windows 7 w/FTK 7 EnCase image, from the Public Catalogs to the same vApp following the instruction of Add Virtual Machines to a vApp (Page 8 in RLES vCloud User Guide) with the following setting:
· Set network to be Net_Network
· Select DHCP to create an IP address (when you use DHCP, fencing option is NOT necessary.)
Note: If you get an error when trying to start a vApp (or a VM within a vApp), try these steps:
1. Open up your vApp and click on the Virtual Machines tab. Right-click your VM and choose "Properties".
2. Click on the Hardware tab. At the bottom of the page, click on the MAC address and choose "Reset".
3. Click OK. When it asks if you want to enable guest customization, click No.
4. Give it a minute to update your VM, then try starting it.
Power on the Windows Virtual machine and login to the system with:
Username: Student
Password: student
EnCase 7 is installed on the virtual machine. When you start the EnCase application, you should see “EnCase Forensic (not Acquisition)” on the top of the application.
EnCase 7 Tutorial
· The EnCase Forensics V7 User Guide posted in myCourses under Hands-on Labs.
· EnCase 7 Essentials webinar series at http://www.encaseondemand.com/EnCasev7Essentials/tabid/2617/index.aspx
The following image files will be used for this lab and they are located in the local drive E:\
1) WinLabRaw.img – Raw Image from dd
2) WinLabEnCase.E01 -- EnCase evidence file
Note: “WinLabEnCase Image” in this documentation = “Lab5 image” in your EnCase image.
PART I: Familiar with EnCase
Exercise 1: Starting a New Case
Launch EnCase for Windows – make sure that you are in the EnCase forensics mode (on the top of the software, you should see EnCase Forensic Training, NOT acquisition mode.)
Click the “New Case” button under CASE FILE to begin a new case.
Use the #1 Basic Template and name the case “Case 1”
Record the defaults that EnCase gives you for its folders. It is safe to use these defaults in our experiments.
Add a Raw Image to the exist case
You can add a raw disk image, for example, the dd image, to your case.
Click EVIDENCE > Add Evidence, then click Add Raw Image
Enter “WinLabRaw Image” in the “Name” field.
Under “Image Type” choose “Disk” and click “OK”.
Under Component Files, click New, locate and select the “WinLabRaw.img” file from E:\
The image will now be added to your case. Double clic.
Similar to Tutorial_Tricentis_Tosca_Testsuite.pdf (20)
A Free 200-Page eBook ~ Brain and Mind Exercise.pptxOH TEIK BIN
(A Free eBook comprising 3 Sets of Presentation of a selection of Puzzles, Brain Teasers and Thinking Problems to exercise both the mind and the Right and Left Brain. To help keep the mind and brain fit and healthy. Good for both the young and old alike.
Answers are given for all the puzzles and problems.)
With Metta,
Bro. Oh Teik Bin 🙏🤓🤔🥰
How to Manage Reception Report in Odoo 17Celine George
A business may deal with both sales and purchases occasionally. They buy things from vendors and then sell them to their customers. Such dealings can be confusing at times. Because multiple clients may inquire about the same product at the same time, after purchasing those products, customers must be assigned to them. Odoo has a tool called Reception Report that can be used to complete this assignment. By enabling this, a reception report comes automatically after confirming a receipt, from which we can assign products to orders.
🔥🔥🔥🔥🔥🔥🔥🔥🔥
إضغ بين إيديكم من أقوى الملازم التي صممتها
ملزمة تشريح الجهاز الهيكلي (نظري 3)
💀💀💀💀💀💀💀💀💀💀
تتميز هذهِ الملزمة بعِدة مُميزات :
1- مُترجمة ترجمة تُناسب جميع المستويات
2- تحتوي على 78 رسم توضيحي لكل كلمة موجودة بالملزمة (لكل كلمة !!!!)
#فهم_ماكو_درخ
3- دقة الكتابة والصور عالية جداً جداً جداً
4- هُنالك بعض المعلومات تم توضيحها بشكل تفصيلي جداً (تُعتبر لدى الطالب أو الطالبة بإنها معلومات مُبهمة ومع ذلك تم توضيح هذهِ المعلومات المُبهمة بشكل تفصيلي جداً
5- الملزمة تشرح نفسها ب نفسها بس تكلك تعال اقراني
6- تحتوي الملزمة في اول سلايد على خارطة تتضمن جميع تفرُعات معلومات الجهاز الهيكلي المذكورة في هذهِ الملزمة
واخيراً هذهِ الملزمة حلالٌ عليكم وإتمنى منكم إن تدعولي بالخير والصحة والعافية فقط
كل التوفيق زملائي وزميلاتي ، زميلكم محمد الذهبي 💊💊
🔥🔥🔥🔥🔥🔥🔥🔥🔥
A Visual Guide to 1 Samuel | A Tale of Two HeartsSteve Thomason
These slides walk through the story of 1 Samuel. Samuel is the last judge of Israel. The people reject God and want a king. Saul is anointed as the first king, but he is not a good king. David, the shepherd boy is anointed and Saul is envious of him. David shows honor while Saul continues to self destruct.
Information and Communication Technology in EducationMJDuyan
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 2)-𝐏𝐫𝐞𝐥𝐢𝐦𝐬
𝐄𝐱𝐩𝐥𝐚𝐢𝐧 𝐭𝐡𝐞 𝐈𝐂𝐓 𝐢𝐧 𝐞𝐝𝐮𝐜𝐚𝐭𝐢𝐨𝐧:
Students will be able to explain the role and impact of Information and Communication Technology (ICT) in education. They will understand how ICT tools, such as computers, the internet, and educational software, enhance learning and teaching processes. By exploring various ICT applications, students will recognize how these technologies facilitate access to information, improve communication, support collaboration, and enable personalized learning experiences.
𝐃𝐢𝐬𝐜𝐮𝐬𝐬 𝐭𝐡𝐞 𝐫𝐞𝐥𝐢𝐚𝐛𝐥𝐞 𝐬𝐨𝐮𝐫𝐜𝐞𝐬 𝐨𝐧 𝐭𝐡𝐞 𝐢𝐧𝐭𝐞𝐫𝐧𝐞𝐭:
-Students will be able to discuss what constitutes reliable sources on the internet. They will learn to identify key characteristics of trustworthy information, such as credibility, accuracy, and authority. By examining different types of online sources, students will develop skills to evaluate the reliability of websites and content, ensuring they can distinguish between reputable information and misinformation.
5. 2 Tosca Tutorial
The purpose of this tutorial is to become acquainted with the basic functions in
Tosca Commander™. You will create a test case for the Tricentis Vehicle
Insurance Application (http://sampleapp.tricentis.com) and you will then execute
this test case.
Chapter overview
We recommend that you go through this tutorial chapter by chapter in the given
order since the contents are explained step by step:
n In chapter 3 "Preconditions for working through the Tutorial" you will find
software requirements and browser settings that need to be specified.
n Chapter "Definition of Terms for the Tosca Commander™ Objects" provides
you with basic terms in Tosca and shows you how to build test cases.
n In chapter 5 "Starting Tosca Commander" you will learn how to start Tosca
Commander, how to open the tutorial, how Tosca workspaces look like and
how to work with Tosca Commander.
n In chapter 6 "The Tricentis Sample Application" we will explain the Tosca
sample application to you.
n Chapter "Creating Modules" illustrates why you need modules, and you will
also create your own modules for your test case.
n In chapter 8 "Creating TestCases" we will explain how to build and manage test
cases in Tosca, and you will create your first test case and add test steps.
n Chapter "Executing TestCases" provides you with a detailed description of
execution lists and the Scratchbook. Here you will create an execution list for
your test case.
Help
If you would like to open the Tosca Manuals online, simply press the F1 key in
Tosca Commander. In our Support Portal you can either browse through the
Online Help or you can download the Tosca Manuals as PDF versions.
Useful links that may be of interest to you
n Webinars
n Online Training
2 Tosca Tutorial
Version 10.0 5
6. 3 Preconditions for working through the Tutorial
In order to go through this tutorial you need:
n A complete default installation of Tricentis Tosca Testsuite along with a valid
license
n Microsoft® Internet Explorer 9 or later and zoom settings set to 100% (see also
the System Requirements for Tricentis Tosca Testsuite).
n A stable internet connection to be able to view all the contents that are related
to this tutorial.
Paths
All specified paths refer to a default installation on drive C: with the default
paths recommended by Tosca.
n Tosca program files %TRICENTIS_HOME%: C:Program FilesTRICENTISTosca
Testsuite, or C:Program Files (x86)TRICENTISTosca Testsuite
n Tosca Commander™ project files %TRICENTIS_PROJECTS%: C:Tosca_
PROJECTS
3 Preconditions for working through the Tutorial
Version 10.0 6
7. 4 Definition of Terms for the Tosca Commander™
Objects
This chapter provides you with definitions of the basic terms in Tosca and it
outlines how TestCases are structured in Tosca.
In this tutorial you will create Modules and a TestCase with TestSteps, and finally
you will run your TestCase.
A TestCase consists of several TestSteps which determine the test process. Each
TestStep maps one page of the Tricentis sample application (also known as "the
test object"). TestSteps are processed in sequential order (see chapter 8 "Creating
TestCases").
You specify your test data in the TestStepValues of the TestSteps. Test data are
data which are used in the application upon test execution. This is for instance
the case when a specific text is written to an input field, or when a button is
clicked.
Automated TestSteps are based on Modules. Modules contain technical
information which is used to identify and steer screen items. These items can for
instance be buttons or input fields. Tosca creates a ModuleAttribute for each
item and saves this to the Module (see chapter 7 "Creating Modules").
In Tosca, test data are separated from technical steering information. This allows
Modules to be used repeatedly to create various TestSteps for any number of
TestCases in order to test a variety of data.
ExecutionLists enable you to run your TestCases and to log the results of the test
execution (see chapter 9 "Executing TestCases").
Icon Object Description
Modules Represent the technical steering information
TestCases Determine the test sequence and contain test
data
ExecutionLists Serve to plan and manage the test execution
Table 1: Objects in Tosca Commander™
Object hierarchy
All objects in Tosca Commander are arranged in a strict hierarchical structure.
This object hierarchy must be kept when objects are either copied or moved
around. This means for instance that TestCase folders cannot be copied to
TestStep folders or Module folders (see chapter "Drag and drop").
Related chapters
n Tosca Commander Manual - chapter Managing workspaces (Object hierarchy).
4 Definition of Terms for the Tosca Commander™ Objects
Version 10.0 7
8. 5 Starting Tosca Commander
TestCases are created, executed and organized in Tosca Commander™.
Start Tosca Commander™ via the Windows Start menu: Start->All
Programs->Tricentis->Tosca Testsuite->Tosca Commander.
As soon as Tosca Commander is open, the start screen will be shown.
Illustration 1: Tosca Commander start screen
Creating workspaces
You need to create a workspace where you will manage your objects.
Select Project->New from the Tosca Commander™ menu to open the
Tosca Commander: Create new workspace window.
Enter the name of your workspace into the Select name for new
workspace field, e.g. Tosca_Tutorial_en.
5 Starting Tosca Commander
Version 10.0 8
9. Illustration 2: Creating a new workspace
Click on OK to create the workspace.
In the next window, click on Close.
The workspace opens.
Illustration 3: Workspace
Tosca Commander™ is inspired by Microsoft Windows Explorer®, which means
that all items are mapped in a tree structure. You can open any number of
windows and display a freely definable section of this tree structure.
If you select an item in the tree view, Tosca will show the item details in the
details view.
5 Starting Tosca Commander
Version 10.0 9
10. If the German user interface in Tosca Commander™ is active, you
can change the language via the following menu entry: Project-
>Options->Ansicht->Sprache. Set option Sprache to English. Tosca
Commander must be restarted so that the changes take effect.
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 you with
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 you switch between the windows of the various sections (see chapter "Windows
and tabs") or if you select objects within the sections, Tosca will open up an
additional tab for this section that includes a dynamic menu. The dynamic menu
shows relevant options for the selected section or object.
A dynamic menu is available for the following sections in Tosca Commander:
TestCases, Modules, Requirements, TestCaseDesign, Execution and Reporting.
Within the Execution section, a dynamic menu is available for the subsections
ExecutionLists and Exploratory Testing.
Status bar
The status bar shows the action that is currently performed by Tosca
Commander.
Windows and tabs
Each object type (e.g. TestCases, Modules, etc.) of the Tosca Commander
workspace has its own window. At the bottom of each window you can see a tab
for each window. Please feel free to arrange the windows according to your
needs.
Go to the Home menu and click on Section->Modules to open a new
Modules window.
Left-click onto the title bar of the Modules window and drag the
window onto the icon in the right section of the window as shown in
the picture below.
5 Starting Tosca Commander
Version 10.0 10
11. Illustration 4: Arranging windows in the workspace
In this example we will insert the Modules window right next to the TestCases
window:
Illustration 5: Two windows
In Tosca you can modify the tabs order at the bottom of the window and you can
drag tabs to other windows, as you like.
Click on the Execution tab in the left window.
Right-click onto the ExecutionLists folder and select the option Open in
new window.
5 Starting Tosca Commander
Version 10.0 11
12. Illustration 6: Open in new window option
The ExecutionLists window opens.
Drag the ExecutionLists window onto the Modules window and drop it
there.
Illustration 7: Moving the ExecutionLists window
You can also use the tabs to rearrange your workspace windows:
simply click on the tab you would like to move and drag this to the
position of your choice.
Click on the x sign to close tabs you don't need.
5 Starting Tosca Commander
Version 10.0 12
13. Close both the Modules and the Execution tab in the left window.
The windows and tabs in your workspace should now look like in the picture
shown below since this is the view we will be working with in this tutorial.
Illustration 8: Recommended view
Perspectives
In Tosca you can arrange any open windows as you like and you can save your
customized view as Perspective. So, if you accidentally change your window
arrangements you can easily restore your preferred view.
Go to the View menu and select Manage->Save... from the Perspectives section
to save your current perspective. The option Manage->Select enables you to
select either the default perspective or one of your saved perpectives if you
created some.
Tree view
In Tosca you can hide the tree view if necessary. Simply click on the vertical line
between the two window sections.
If you click once again onto the vertical divider line, the tree view will be shown
again.
5 Starting Tosca Commander
Version 10.0 13
14. Illustration 9: Tree view is visible
Illustration 10: Hidden tree view
You can resize you workspace windows if required: left-click onto the divider line,
hold the mouse button down and move the vertical divider line to you preferred
position.
Project window
The project window provides you with an overview of your entire project (Home-
>Project). This shows all workspace objects in a tree view starting from the
project root element which is named Tosca_Tutorial_en in this tutorial.
Context menu and mini toolbar
In Tosca you are able to process workspace objects via the context menu or the
dynamic menu. The context menu provides you with the options that are relevant
5 Starting Tosca Commander
Version 10.0 14
15. for the respective object.
Open the context menu by right-clicking on any object in the workspace.
The upper part of the context menu includes a mini toolbar. This is part of the
context menu and it contains options that are frequently used, such as Delete ,
Rename and options for creating new objects. Hover over the icons in the mini
toolbar to view the option name in the tooltip.
Go to the TestCases section. Right-click on the TestCase folder
TestCases and select the option Create Folder from the mini toolbar.
Illustration 11: Creating a new folder
Rename the new TestCase folder to My first TestCase.
Right-click on the TestCase folder My first TestCase and select the
option Create Folder from the mini toolbar.
Rename the new TestCase folder to Vehicle Insurance.
Illustration 12: New TestCase folder Vehicle Insurance
TestCase folders can be renamed at any point in time. Simply select
the option Rename from the context menu.
Create a copy of the TestCase folder Vehicle Insurance beneath the TestCase
folder.
Right-click on the Vehicle Insurance folder and select the option Copy
from the context menu.
The copy must be created within the TestCase folder My first TestCase so that
this is located on the same level like the TestCase folder Vehicle Insurance.
5 Starting Tosca Commander
Version 10.0 15
16. Select the option Paste from the context menu of the TestCase folder
My first TestCase.
Tosca automatically assigns the name Vehicle Insurance_1 to the newly created
copy.
Illustration 13: Vehicle Insurance_1 folder
Drag and drop
In Tosca Commander you can perform various operations by using drag and
drop.
Left click on the TestCase folder Vehicle Insurance_1 and keep the
mouse button pressed. Without releasing the mouse button, drag the
TestCase folder Vehicle Insurance_1 over the TestCase folder Vehicle
Insurance. Release the mouse button as soon as the cursor is located
on the TestCase folder Vehicle Insurance.
Illustration 14: Moving TestCase folders by using drag and drop
As you can see, TestCase folder Vehicle Insurance_1 is now located beneath the
TestCase folder Vehicle Insurance:
Illustration 15: TestCase folder Vehicle Insurance_1 as a subfolder
Since you don't need TestCase folder Vehicle Insurance_1 any longer you can
delete this as follows:
Right-click onto the TestCase folder Vehicle Insurance_1 and select the
option Delete from the mini toolbar.
5 Starting Tosca Commander
Version 10.0 16
17. In the next step, try to move the TestCase folder Vehicle Insurance to the
Modules folder Modules.
Drag the TestCase folder Vehicle Insurance onto the Modules folder
Modules.
Tosca will prevent this operation since TestCase folders may only be
positioned hierarchically beneath TestCase folders (see also chapter "Object
hierarchy").
Editing columns
In the details view you can add columns, move or remove them, as required.
Use drag and drop to move the DataType column to the right of the
Workstate column. Two arrows mark the position where the column
will be inserted.
Illustration 16: Moving a column
Right-click onto the header of a column, and select the option Column
Chooser from the context menu. A window opens containing a list of
available columns.
Illustration 17: Opening the Column Chooser
Use drag and drop to move the entry Description to the required
column position. Two arrows mark the position where the new column
will be inserted.
5 Starting Tosca Commander
Version 10.0 17
18. Illustration 18: Adding a column
Left-click onto the header of the Description column, keep the mouse
button pressed and drag this column down until the cursor's shape
turns into an X, then release the mouse button. The column is now
removed from this view.
Illustration 19: Removing a column
Related chapters
n Tosca Commander Manual - chapter Working with Tosca
n Tosca Commander Manual - chapter Creating and Managing Workspaces
n Tosca Commander Manual - chapter Managing workspaces (Object hierarchy)
5 Starting Tosca Commander
Version 10.0 18
19. 6 The Tricentis Sample Application
In this tutorial, the Tricentis sample application will serve as object to be tested,
and you will use this application to create a TestCase.
The Tricentis sample application is a fictitious vehicle insurance premium
calculator and can be used to create quotes for various vehicle types.
Open the Tricentis sample application at
http://sampleapp.tricentis.com. Please make sure that you use
Microsoft® Internet Explorer (see chapter 3 "Preconditions for working
through the Tutorial").
Illustration 20: Tricentis Sample Application: start screen
Click on the Automobile link in the navigation bar.
Now you can see the start screen of the vehicle insurance premium calculator
which allows you to enter vehicle data. Mandatory fields are marked with an
asterisk *.
6 The Tricentis Sample Application
Version 10.0 19
20. Illustration 21: Vehicle insurance premium calculator: entering vehicle data
Feel free to get yourself acquainted with the Tricentis sample application: enter
some data into the input fields and click Next.
Click on Home in the submenu of the navigation bar to return to the
start screen of the Tricentis sample application.
6 The Tricentis Sample Application
Version 10.0 20
21. 7 Creating Modules
If you would like to create an automated TestCase for the Tricentis sample
application you need to create Modules which contain the required steering
information (see chapter 4 "Definition of Terms for the Tosca Commander™
Objects").
Your task in this tutorial is to build an automated TestCase which contains data
for an automobile, and to create a quote for a vehicle insurance with these data.
To gather all this information you need to create Modules for each screen of the
Tricentis sample application (see chapter 6 "The Tricentis Sample Application").
In Tosca we refer to the creation of Modules as Scanning. Tosca analyzes the
screen contents and searches for steerable items. You can then select the items
you need and create a Module in Tosca. The Module contains all information
required for steering the relevant items.
Right-click on the Module folder Modules and select the option Create
Folder from the mini toolbar. You can also click on the Module folder
and select the icon Create Folder->Folder from the dynamic menu
Modules.
Assign the name My first Modules to the new Module folder.
Select the option Create Folder from the context menu of the Module
folder My first Modules. You can also click on the Module folder and
select the icon Create Folder->Folder from the dynamic menu
Modules.
Assign the name Vehicle Insurance to the new Module folder.
Illustration 22: Module folder Vehicle Insurance
Module 1: Start screen (Home)
The first page of the Tricentis sample application is the start screen. Please make
sure that the start screen is open in your browser since Tosca always scans the
screen that is currently available.
Click on Home in the navigation bar of the sample application to open
the start screen.
7 Creating Modules
Version 10.0 21
22. Illustration 23: Tricentis sample application: start screen
Now you're ready to scan this screen.
Return to Tosca Commander, go to the Modules window and right-click
on the Module folder Vehicle Insurance you created earlier. Select the
option Scan Application->Desktop from the context menu. You can
also click on the Module folder and select the option from the dynamic
menu Modules.
The XScan window opens:
7 Creating Modules
Version 10.0 22
23. Illustration 24: XScan window
Tosca XScan loads all applications that are currently open.
Click on the window which shows the Tricentis sample application and
then click on Start in the lower right corner of the XScan window.
Wait a few seconds while Tosca scans the screen.
7 Creating Modules
Version 10.0 23
24. Illustration 25: Tosca XScan: Home screen
The HOME window now displays all items which were found during the scan
process. Although a large amount of items and functions will be shown in the
XScan window, most of them are not relevant for this example.
Search for the items that you need for your Module: The relevant item on the
start screen is the Automobile link located in the navigation bar.
Enable the checkbox in front of an item to select this.
If you would like Tosca to help you identify the items in the XScan
window and the browser, you can use the Mark on Screen function.
Enable this option in the upper part of the XScan window and select
an item from the tree. Tosca will then highlight this in red in the
browser window.
7 Creating Modules
Version 10.0 24
25. Illustration 26: Highlighting items
Enable the checkbox next to the item Automobile.
Rename the root element Tricentis Vehicle Insurance to Home. The
Module will then be saved under Home.
Illustration 27: Tosca XScan: selecting the relevant item Automobile of the start screen
Click on Save in the XScan window and close the window.
Tosca creates the Module Home in the Module folder Vehicle Insurance. The item
Automobile you have selected earlier is now shown in the Module as
ModuleAttribute. The Module holds any information that is required to click the
link in the sample application.
7 Creating Modules
Version 10.0 25
26. Illustration 28: Home Module
You will need this Module later on for your TestCase (see chapter 8 "Creating
TestCases").
Switch to the Tricentis sample application and click the Automobile link
on the start screen.
The Vehicle data screen appears.
Illustration 29: Vehicle data screen
Module 2: Vehicle data
Now you will create a Module for the vehicle data screen.
Right-click on the Module folder Vehicle Insurance and select Scan
Application->Desktop from the context menu. You can also click on
7 Creating Modules
Version 10.0 26
27. the Module folder and select the option from the dynamic menu
Modules.
The XScan window opens.
Click on the browser tab which shows the Tricentis sample application
and then click on Start in the lower right corner of the XScan window.
Wait a few seconds while Tosca scans the screen. The HOME window shows all
items found upon scanning. Search for the items that are relevant for your
Module:
Select the items to be included in the Module as shown in the
illustration below.
Assign the following meaningful name to the root element: Vehicle
data.
7 Creating Modules
Version 10.0 27
28. Illustration 30: Tosca XScan: relevant items for the Vehicle data Module
Click on Save in the XScan window and close the window.
Tosca creates the Vehicle data Module in the Module folder Vehicle Insurance
and adds all items you have selected in the XScan window as ModuleAttributes.
7 Creating Modules
Version 10.0 28
29. Switch to the Tricentis sample application, enter the data as shown in
the illustration below and click on Next.
Illustration 31: Entering vehicle data
The Insurant screen appears.
7 Creating Modules
Version 10.0 29
30. Illustration 32: Insurant data screen (partial view)
Module 3: Insurant
Now you will create a Module for the Insurant screen.
Right-click on the Module folder Vehicle Insurance and select Scan
Application->Desktop from the context menu. You can also click on
the Module folder and select the option from the dynamic menu
Modules.
The XScan window opens.
Click on the browser tab which shows the Tricentis sample application
and then click on Start in the lower right corner of the XScan window.
Wait a few seconds while Tosca scans the screen.
Enable the option Select on Screen in Tosca XScan. This will help you
select the correct items with ease.
7 Creating Modules
Version 10.0 30
31. Illustration 33: Tosca XScan: Select on Screen
The Select your controls on the screen window opens:
Illustration 34: Tosca XScan: Select your controls on the screen window
Click onto an item in the Tricentis sample application. Tosca will
highlight the corresponding item in blue in the application and will
automatically add this to the Select your controls on the screen
window.
7 Creating Modules
Version 10.0 31
32. Illustration 35: Tosca XScan: Select your controls on the screen window: First Name is selected
To remove an item from this list, simply click on this item again.
Select the items to be included in your Module as shown in the
illustration below.
Illustration 36: Tosca XScan: Insurant data are selected, part 1
Click on as soon as you're finished. The focus will return to the
Tosca XScan window.
You can open the Select your controls on the screen window again
at any time via the Tosca XScan menu to add further items to your
Module.
Switch to the Tricentis sample application and scroll down on the
current page to display the items as shown in the illustration below.
7 Creating Modules
Version 10.0 32
33. Illustration 37: Tricentis sample application: Insurant details
Enable the Select on Screen option in Tosca XScan and select the items
that are still missing as shown in the illustration below.
Illustration 38: Tosca XScan: Insurant data are selected, part 2
Rename the project root element to Insurant.
7 Creating Modules
Version 10.0 33
34. Illustration 39: Tosca XScan: relevant screen items for the Insurant Module
If you are wondering why the Prev button is not enabled in the list
above, it’s just because it is not needed in this TestCase.
Click on Save in the XScan window and close the window.
Tosca creates the Module Insurant in the Module folder Vehicle Insurance and
adds all items you have selected in the XScan window as ModuleAttributes.
Switch to the Tricentis sample application, enter the insurant data as
shown in the illustration below and click on Next.
7 Creating Modules
Version 10.0 34
35. Illustration 40: Entering insurant data
The Product data screen appears:
7 Creating Modules
Version 10.0 35
36. Illustration 41: Product data screen
Module 4: Product data
Now you will create a Module for the product data screen.
Right-click on the Module folder Vehicle Insurance and select Scan
Application->Desktop. You can also click on the Module folder and
select the option from the dynamic menu Modules.
The XScan window opens.
Click on the browser tab which shows the Tricentis sample application
and then click on Start in the lower right corner of the XScan window.
Wait a few seconds while Tosca scans the screen.
Select the items to be included in the Module as shown in the
illustration below.
7 Creating Modules
Version 10.0 36
37. Illustration 42: Tosca XScan: relevant items for the Product data Module
Rename the two Yes items to Euro Protection and Legal Defense
Insurance accordingly:
To do so, enable the Mark on Screen option in Tosca XScan and select
the Yes items in the tree view. This allows you to easily identify and
distinguish these two items from each other.
Illustration 43: Tosca XScan: identifying items by using Mark on Screen
Assign the following meaningful name to the root element: Product
data.
7 Creating Modules
Version 10.0 37
38. Illustration 44: Tosca XScan: relevant items for the Product data Module
Click on Save in the XScan window and close the window.
Tosca creates the Module Product data in the Module folder Vehicle Insurance
and adds all items you have selected in the XScan window as ModuleAttributes.
Switch to the Tricentis sample application, enter the data as shown in
the illustration below and click on Next.
Indicate the first of the month after next for the Start Date. In our tutorial here,
we use 12/01/2016.
Illustration 45: Entering product data
7 Creating Modules
Version 10.0 38
39. The Price option screen appears. Please note that the amounts in your sample
application may differ from the ones shown in the illustration below.
Illustration 46: Price option screen
Module 5: Quote
On this page you can choose from various packages and price options. Later on
you will create a TestCase using data of this screen to verify whether the Price per
Year ($) equals a certain value for the corresponding package. This means that
you need to scan a new Module right now:
Right-click on the Module folder Vehicle Insurance and select Scan
Application->Desktop. You can also click on the Module folder and
select the option from the dynamic menu Modules.
The XScan window opens.
Click on the browser tab which shows the Tricentis sample application
and then click on Start in the lower right corner of the XScan window.
Wait a few seconds while Tosca scans the screen.
The insurance calculator shows the calculated quote in the form of a table.
Please note that the amounts in your sample application may differ from the
ones shown in the illustration below.
Illustration 47: Selecting the appropriate package
Use the Mark on Screen option in the XScan window to identify the
table accordingly. The table name in XScan is priceTable.
Select the items to be included in the Module as shown in the
illustration below.
7 Creating Modules
Version 10.0 39
40. Assign the following meaningful name to the root element: Quote.
Illustration 48: XScan: relevant items for the Quote Module
Click on Save in the XScan window and close the window.
Tosca creates the Module Quote in the Module folder Vehicle Insurance and
adds all items you have selected in the XScan window as ModuleAttributes.
At this stage you have created all the Modules you need for your TestCase.
7 Creating Modules
Version 10.0 40
41. Illustration 49: Modules required for the Automobile TestCase
Related chapters
n Tosca Commander Manual - chapter Modules section (orange)
7 Creating Modules
Version 10.0 41
42. 8 Creating TestCases
In this chapter you will create a TestCase with TestSteps which maps the vehicle
insurance quote for an automobile. This requires that you specify the automobile
data in the TestSteps in order to create the quote. Finally you should verify a
specific value of your quote.
In the previous chapter "Creating Modules" you have already scanned all the
required Modules, and in this chapter you will create a TestCase with TestSteps
which include the test data required for running this TestCase in the end.
Creating a TestCase
Create the TestCase Automobile in your TestCase folder Vehicle Insurance. You
have already created this folder in chapter "Context menu and mini toolbar".
Right-click on the TestCase folder Vehicle Insurance and select Create
TestCase from the mini toolbar. You can also click on the TestCase
folder and select the icon Create Object->TestCase from the
dynamic menu TestCases.
Assign the name Automobile to the new TestCase.
Illustration 50: Automobile TestCase
The TestCase starts off with the start screen of the Tricentis sample application.
8 Creating TestCases
Version 10.0 42
43. Illustration 51: Tricentis sample application: start screen
TestStep 1: Start screen (Home)
Your first TestStep should instruct Tosca to click on the Automobile link in the
Tricentis sample application to start the vehicle insurance calculator.
Illustration 52: Navigation bar
You have already created the Module Home earlier (see also "Module 1: Start
screen (Home)"), and you will be using this Module now for your first TestStep.
Switch to the Modules window, drag the Home Module onto your
Automobile TestCase and drop it there.
8 Creating TestCases
Version 10.0 43
44. Illustration 53: Creating the Home TestStep
Tosca creates the TestStep Home and automatically assigns the name of the
corresponding Module to this. All the TestStepValues that can be steered are
located beneath this TestStep - in our case, the Automobile link of the start
screen Home. The TestStepValue icons are grayed out until you define actions for
these values.
TestStepValues which are grayed out due to lacking values can either
be hidden from view or shown via the F9 key.
Open the drop-down menu in the Value column for the TestStepValue
Automobile, select {Click} and press Enter to confirm your selection.
Illustration 54: Defining actions for the Home screen
The ActionMode column is automatically set to Input since you have defined an
input action.
Illustration 55: Finalized Home TestStep
8 Creating TestCases
Version 10.0 44
45. You've just created your first TestStep!
TestStep 2: Vehicle data
This TestStep should enter vehicle data and should then click on Next.
Return to the Modules window, drag the Vehicle data Module onto
your Automobile TestCase and drop it there.
The Vehicle data TestStep is inserted beneath the Home TestStep.
Enter the data into the TestStep as shown in the illustration below.
TestStepValues provide values that are stored in the ValueRange
column of the corresponding ModuleAttribute in a drop-down list. If
your required value is not available in this list, you can also enter
this manually.
Illustration 56: Finalized Vehicle data TestStep
The ActionMode column of the TestSteps is automatically set to Input again since
you have defined input actions.
TestStep 3: Insurant
This TestStep should enter insurant data and should then click on Next.
Return to the Modules window, drag the Insurant Module onto your
Automobile TestCase and drop it there.
The Insurant TestStep is inserted beneath the Vehicle data TestStep.
Enter data into the TestStep as shown in the illustration below.
8 Creating TestCases
Version 10.0 45
46. Illustration 57: Finalized Insurant TestStep
Let's continue with the next TestStep.
TestStep 4: Product data
This TestStep should select the according product and should then click on Next.
Return to the Modules window, drag the Product data Module onto
your Automobile TestCase and drop it there.
The Product data TestStep is inserted beneath the Insurant TestStep.
Enter values into the TestStep as shown in the illustration below.
Please enter the first of the month after next for the TestStepValue
Start Date. In this tutorial we used the date 12/01/2016.
Illustration 58: Finalized Product dataTestStep
8 Creating TestCases
Version 10.0 46
47. TestStep 5: Quote
This is the final TestStep in your TestCase. Here Tosca should verify whether the
Price per Year ($) for the Ultimate package equals a specific value.
The vehicle insurance calculator shows the calculated values along with various
options in a table. Please note that your Price per Year ($) value may differ from
the one in this tutorial (685,00). You may use the value Tosca calculated for you in
your sample application.
Illustration 59: Quote data
Return to the Modules window, drag the Quote Module onto your
Automobile TestCase and drop it there.
The Quote TestStep is inserted beneath the Product data TestStep.
Illustration 60: Quote TestStep
Define the cell which includes the value to be verified in the TestStepValue
PriceTable. The amount is shown in the first row of the last column.
Expand the view for the TestStepValue priceTable and open the drop-
down menu of the TestStepValue <Row>.
8 Creating TestCases
Version 10.0 47
48. Illustration 61: Selecting a row from the priceTable
Select $1 from the drop-down list and press Enter. This specifies the
row which holds the value to be verified.
Illustration 62: $1 row
Left-click on the TestStepValue <Cell> beneath the TestStepValue $1.
Illustration 63: Specifying the cell
Select $last from the drop-down list and press Enter. This specifies the
last cell of the row which includes the value to be verified.
8 Creating TestCases
Version 10.0 48
49. Illustration 64: Specifying the cell
Enter the value that should be verified into the Value column of the
new TestStepValue $last.
Use a comma as thousand separator and a dot as decimal separator
when you enter the value to be verified.
Illustration 65: Finalized Quote TestStep
You may have realized that the ActionMode column has automatically been set
to Verify. Unlike in your previous TestSteps where Tosca is supposed to input
data (Input), in this TestStep Tosca should however verify data.
In the first step of this verify operation, Tosca will select the TestStepValue
priceTable and the first row ($1) by using the ActionMode Select. In the next step
it will use the TestStepValue $last to verify whether the value of the last cell
equals 685.00.
Congratulations! You're done with your Automobile TestCase. In the next chapter
you will learn how to create an ExecutionList in order to run your TestCase (see
chapter 9 "Executing TestCases").
Related chapters
n Tosca Commander Manual - chapter TestCases section (blue)
8 Creating TestCases
Version 10.0 49
50. 9 Executing TestCases
In Tosca you can sum up all completed TestCases in ExecutionLists and run
them. Each TestCase is shown as an ExecutionEntry. Execution results and their
history are automatically written to a log file (ActualLog).
If you would like to run specific TestSteps separately or if you would like to check
TestCases that are still incomplete, you can use the Scratchbook function (see
"ScratchBook").
9.1 ExecutionLists
Run your Automobile TestCase in an ExecutionList:
Click on the ExecutionLists tab in Tosca Commander.
Right-click on the ExecutionList folder ExecutionLists and select Create
Folder from the mini toolbar. You can also click on the ExecutionList
folder and select the icon Create Folder->Folder from the dynamic
menu ExecutionLists.
Assign the name My first ExecutionList to the new ExecutionList folder.
Illustration 66: ExecutionLists
Creating ExecutionEntries
In Tosca you can create ExecutionEntries by dragging and dropping TestCases
onto ExecutionLists.
Right-click onto the ExecutionList folder My first ExecutionList and
select Create ExecutionList from the mini toolbar. You can also click on
the ExecutionList folder and select the icon Create Object-
>ExecutionList from the dynamic menu ExecutionLists.
9 Executing TestCases
Version 10.0 50
51. Assign the name Vehicle Insurance to the new ExecutionList.
Drag your Automobile TestCase onto your Vehicle Insurance
ExecutionList and drop it there.
The ExecutionEntry Automobile is automatically created and linked to the
corresponding TestCase.
Illustration 67: ExecutionEntry Automobile
If you would like to see which TestCase is linked to which
ExecutionEntry, simply right-click onto an ExecutionEntry and select
the option Jump to TestCase. You can also click on the
ExecutionEntry and select the icon Jump to TestCase from the
dynamic menu ExecutionLists.
Select the option Jump to Module from the context menu of a
TestStep to see which TestStep is linked to which Module. You can
also click on the TestStep and select the icon Jump to Module
from the dynamic menu TestCases.
Running ExecutionLists
Open the Tricentis sample application in Microsoft® Internet Explorer
(see also chapter 6 "The Tricentis Sample Application").
The sample application must show the start screen so that the TestCase can be
successfully executed.
Switch back to Tosca Commander, go to the ExecutionLists window and
select the option Run from the context menu of the Vehicle Insurance
ExecutionList. You can also click on the ExecutionList and select the
icon Run from the dynamic menu ExecutionLists.
9 Executing TestCases
Version 10.0 51
52. Illustration 68: Running ExecutionLists
Tosca starts executing the TestCase.
Since Tosca will take over control of your mouse and keyboard upon
test execution we highly recommend that you refrain from
performing mouse clicks and keyboard inputs while Tosca is
running your TestCase.
You should now be able to observe Tosca clicking the links and filling out all the
forms in the insurance calculator. The execution will finally stop on the last page
of the Tricentis sample application where you can view the quotes that have been
created for the respective packages.
Execution information
The Loginfo column shows the execution state:
n Green: Passed
n Red: Failed
n White: No Result (i.e. this ExecutionEntry has not yet been executed)
n Gray: the TestCase does no longer exist in this workspace
If your TestCase was successfully executed without any errors, Tosca will indicate
this with a green bar. Since your current TestCase only consists of one single
ExecutionEntry, the green bar includes the figure 1.
Illustration 69: Execution result Automobile
9 Executing TestCases
Version 10.0 52
53. To get an idea of how various execution information is shown in Tosca you will
now create an ExecutionList containing 5 ExecutionEntries:
Switch to the TestCases window and create the TestCase folder Quotes
beneath the TestCase folder My first TestCase.
Copy the TestCase Automobile to the Quotes TestCase folder and
rename this to Automobile_01.
Switch to the Modules window, drag the Quote Module onto your
Automobile_01 TestCase and drop it there.
Tosca will automatically create the TestStep Quote_1.
Select the option {Click} from the drop-down list of the TestStepValue
Home.
Illustration 70: TestStep Quote_1
Tosca will return to the start screen of the Tricentis sample application after it
has created the quote. This allows you to run several TestCases in a row since
each TestCase starts on the start screen of the sample application.
Make 4 copies of your Automobile_01 TestCase and paste them into
the Quotes folder. The TestCases are numbered consecutively.
Illustration 71: TestCases from Automobile_01 to Automobile_05
9 Executing TestCases
Version 10.0 53
54. Drag your Quotes TestCase folder onto your Vehicle Insurance
ExecutionList and drop it there.
Tosca automatically creates new ExecutionEntries and adapts the ExecutionList
statistics accordingly: Since your newly created ExecutionEntries have not yet
been executed, they receive the status No Result and are shown with a white bar
in the Loginfo column.
Illustration 72: White bar showing that 5 ExecutionEntries have not yet been executed
Set the test results manually to see all execution states that are available in
Tosca:
Right-click on the Automobile_01 ExecutionEntry and select Set result-
>Failed from the context menu. You can also click on the
ExecutionEntry and select the icon Set result->Failed from the
dynamic menu ExecutionLists.
Give reasons for your decision by entering Reason 01 into the
appearing popup window.
Set the ExecutionEntries for Automobile_02 and Automobile_03 also to
Failed (Set result->Failed). You don't need to give reasons here, simply
click on OK.
Right-click on the Automobile_04 ExecutionEntry and select Set result-
>Passed from the context menu. You can also click on the
ExecutionEntry and select the icon Set result->Passed from the
dynamic menu ExecutionLists. Confirm your selection with a click on
OK in the appearing popup window.
Switch to the TestCases window and remove TestStep Automobile_02
from your TestCase folder Quotes.
Confirm the appearing warning message with a click on OK.
9 Executing TestCases
Version 10.0 54
55. Illustration 73: Warning
Switch to the ExecutionLists window and left-click on your Quotes
ExecutionList.
The Loginfo column shows various execution states:
One TestCase is marked as passed (green), one has not yet been executed (white),
and one TestCase does no longer exist in the workspace (gray). Two TestCases are
marked as failed (red).
Illustration 74: Execution states
History
To become acquainted with ExecutionList histories, you will now modify a
TestCase and trigger an error. Specify a wrong verification value:
Switch to the TestCases window, go to your Automobile_04 TestCase
(TestCase folder Quotes) and set the value to be verified to 12345 in the
Quote TestStep.
9 Executing TestCases
Version 10.0 55
56. Illustration 75: The value to be verified is wrong
Open the Tricentis sample application in Microsoft® Internet Explorer
(see also chapter 6 "The Tricentis Sample Application").
The sample application must show the start screen so that your TestCase can be
successfully executed.
Run your Quotes ExecutionList.
Disable the option Show only last ActualLog under View-
>ExecutionLists, and enable the following entries: Show multiline Logs,
Show Statistics only on visible ExecutionLists, and Show Statistics.
Illustration 76: ExecutionLists view - settings
Right-click on the ExecutionEntry Automobile_04 in the details view.
Choose (Expand all) in the mini toolbar to view all TestStepValue
9 Executing TestCases
Version 10.0 56
57. details.
The log history is shown in chronological order in Tosca. The most recent results
are always located on top.
The ExecutionEntry Automobile_04 provides a description of the error occurred,
along with further details on which TestStep caused the error.
Illustration 77: ExecutionList: history
9.2 ScratchBook
The ScratchBook in Tosca Commander is used for running individual TestSteps
upon TestCase creation.
You can combine various TestCases, TestSteps and TestCase folders and run
them in the ScratchBook.
In contrast to ExecutionLists, the ScratchBook does neither save how TestCases
are combined for test execution nor the test results. We recommend using the
ScratchBook solely upon test case creation.
Run the Vehicle data TestStep in your Automobile TestCase in the ScratchBook.
Since this TestStep contains vehicle data you have to make sure that the
corresponding page of the sample application is open so that Tosca can enter the
data accordingly.
Open the Tricentis sample application in Microsoft® Internet Explorer
(see "The Tricentis Sample Application") and go to the Vehicle data
page.
9 Executing TestCases
Version 10.0 57
58. Illustration 78: Vehicle data screen
Return to Tosca Commander. Right-click on your Vehicle data TestStep
(beneath the Automobile TestCase) and select the option Run in
ScratchBook from the context menu. You can also click on the TestStep
and select the icon Run in ScratchBook from the dynamic menu
TestCases.
Illustration 79: Running the TestStep in Scratchbook
9 Executing TestCases
Version 10.0 58
59. The ScratchBook window opens and Tosca runs the Vehicle data TestStep.
Since Tosca will take over control of your mouse and keyboard upon
test execution we highly recommend that you refrain from
performing mouse clicks and keyboard inputs while Tosca is
running your TestStep.
The ScratchBook window lists the executed TestSteps. In the illustration below
you can see the Vehicle data TestStep along with the execution results.
Illustration 80: ScratchBook
Congratulations! You've successfully completed this tutorial.
At this stage you should be familiar with the main important processes in Tosca.
Related chapters
n Tosca Commander Manual - chapter ExecutionLists
9 Executing TestCases
Version 10.0 59