Accelerate digital transformation and realize the benefits of efficiency, quality, and cost reduction at scale with codeless, easy-to-use automation platform that seamlessly connects process intelligence, testing and RPA. Learn More. Enablement Services Get the most from your investment at every stage of the automation lifecycle. Managed Services Take a hands-off approach to automation while ensuring ongoing project success. Training Services Accelerate automation success by giving your teams the right training, in the right way, at the right time.
Solutions Ensure your success with comprehensive solutions spanning all three stages of automation—discovery, testing, RPA—in one codeless platform. End-to-End Testing Run end-to-end business process tests for packaged applications with enterprise level controls and reporting. Web Testing Simplify the complexity of web challenges by testing automatically as updates to web applications as they are released.
Cloud Testing Cloud testing allows you to run a huge number of tests in parallel, both locally and remotely, facilitating easier and larger-scale deployments. Mobile Testing Reuse tests, no matter which mobile platform is used, and maintain one test for multiple browsers and devices. Exploratory Testing Extend the power of exploratory testing by automating the discovery and documentation of as-is business processes.
SuccessFactors Business process assurance for your end-to-end HR processes. Concur Ensure quality: test every workflow. Hybris High-speed functional testing for digital commerce. Ariba Ensure crisp execution in eCommerce. Fiori Ensure the highest-quality user experience. PeopleSoft Keep pace with system changes and drive agility. Siebel Ensure quality and high levels of execution end-to-end. JD Edwards Handle complexity and mitigate risk for your application modules.
Salesforce Ensure every CRM and customer-focused function works the way you need it with automated salesforce testing of end-to-end business processes. SuccessFactors Our industry-leading automation is designed to validate end-to-end processes, delivering higher levels of QA across applications, technologies, and interfaces. Industry Spotlight Explore real-world success stories from customers by industry. Partners Experience the power of a best-of-breed technology ecosystem with deep expertise Request Partner Licenses Demonstrate Worksoft's connective automation to your clients by requesting proof of concept POC , pilot or project licenses.
Access Partner Training Courses Access all of our latest training courses to anything and everything Worksoft and our suite of products and solutions. Support We're dedicated to the success of your organization. Take a look at our full list of support options and we'll do our best to assist.
This gives you the option to create one process with these steps, and then call that process as a sub-process. Certify provides several options for executing processes against your application, including running an unattended process or suite of processes, running processes step-by-step, and running in debug mode. Process execution is discussed in detail in lesson 2. User defined attributes can be added to store additional data with the results.
This data can be exported for additional analysis or tracking. If you have created links between processes and requirements, Certify provides a Requirement coverage report that allows you to analyze whether the requirements for your application are satisfied.
You can create as many folders and subfolders as necessary to contain the processes for your projects. The folder names you use should be descriptive of the processes contained within them. As a best practice, use a similar naming convention to the one used for naming processes discussed previously. You can create folders by right-clicking the project folder or an existing folder in the Navigation tree and selecting New Folder, or by copying and pasting folders to create new folders.
In the following exercises, you will define and add the steps for all the supporting processes that were identified. On the Navigation taskbar, click Processes. In the Navigation tree, click the plus sign next to folder. Click the plus sign next to the Sandbox folder. Right-click Sandbox and select New Folder. The New Folder dialog box appears. In the Name field, type your name.
The folder appears under Sandbox in the Navigation tree. To create the sub-folder to hold the processes: a. Right-click your name and select New Folder. The folder appears under your name in the Navigation tree. You can create steps in a new process or insert steps in existing processes by clicking on one or more object s in the SAP application. LiveTouch inserts corresponding process steps for each of the selected objects.
LiveTouch also prepopulates the appropriate step parameters with values entered into or produced by the SAP application. LiveTouch allows you to learn multiple windows in one session. You can assess a window and learn the objects on that window. Next, click the Pause button and then go to another window in your SAP application.
Lastly, click the Start button and learn the objects on that window, all in the same session. Learn Settings Fields Show when hovering mouse As you hover over objects in the application, the field information is displayed. Learn Objects as Needed Learn new objects while adding steps to your process. Save Objects to Application Version Save the newly learned objects to a specific application version.
Target Folders Select a target folder for the variables. Note: This feature is only available to users who purchased Certify Data. After completing a step, the next step is executed until the last step has completed. Create a separate process is recommended any time a step sequence is different. For example, creating a new account transaction uses different steps than deleting an account transaction.
In the Navigation tree, click the Sandbox folder, and then click your name. Right-click in the Summary pane and select New Process. The Process Editor appears.
This is where you will define your processes and add the steps using the SAP application. Give the process a name and description: a. In the Description field, type Process will create a standard sales order.
If you need to assign an owner to the process, simply click the Assign Owner button. The Select Process Owner window appears. You can assign a process to a user or a group. The default is User. You can also assign a Team to the process by typing the name of the team in the Team field. If you need to change the process owner, click the Clear Owner button to clear the field. This step is optional.
Now, we will create a process. For more information on creating processes, refer to the Process and Data Editor tutorial. Click the Steps tab. Right-click in the Steps tab and select New. Click the Application Version drop-down arrow and select System 1. Click the Window drop-down arrow and select System. Click the Object drop-down arrow and select Execution. Click the Action drop-down arrow and select Execute Process. At the bottom of the screen, in the Parameters tab, in the Process field, select the New process icon.
To rename the process, in the Navigation tree, click Untitled. Certify dialog box appears asking to save the current process. Click Yes. Click the Process Details tab.
In the Description field, type Executes VA01 transaction and inputs initial sales data. Remember, to use LiveTouch, you have to open the SAP application and navigate to the screen that you will use.
In Certify, right-click in the Steps area and select New. A red highlight appears around the object and the information from the object appears in the Certify LiveTouch dialog box.
The Certify Process and Data Editor appears. In the Steps area, a step has been inserted for the object and the step is pre-populated with the application version, window, object, and action.
There are several ways to execute a step. Once you highlight the step, you can: 1 click Action from the menu and select Execute Step, 2 press the F6 function key, or 3 right-click on the step and select Execute Step. To execute the step: a. In the Steps area, highlight the step. Right-click on the step and select Execute Step. In Certify, notice the status bar. It displays the results of the process. As you can see, the process passed. Verify that the fields are pre-populated with data.
In Certify, in the Steps area, right-click Step 1. Select the following object fields by clicking in the object fields: f. In the Certify LiveTouch dialog box, click Pause. Notice that the LiveTouch window is still available. In the Certify LiveTouch dialog box, click Start. Select the following objects fields by clicking in the object fields: - Sold-to-party - Ship-to-party - PO Number - PO Date - Material Table When you LiveTouch a table or a grid, be sure the red border surrounds the entire table or grid as shown in the screenshot below.
A red highlight appears around the objects and the information from the last object selected appears in the Certify LiveTouch dialog box. Notice the status bar shows 10 objects selected. That is the total from both windows. In the Steps area, a step has been inserted for each selected object and the steps are pre-populated with the application version, window object, and action.
Now, we will add system variables to steps. A variable is a symbol or name that represents a value. Variables contain a specific type of value that can be inserted into a field, acted on, or stored for future comparison against another value.
To select a variable for the PO Number field: a. The Select Variable window appears. In the tree, click the System Variables folder. In the Variables pane, select Date. The variable name appears in the Value to Input field with v preceding the name, indicating it is a variable. Click the drop-down arrow in the Format field and select Timestamp.
PO numbers normally have to be unique. The Date variable, along with the timestamp format allows for an original PO number. To select a variable for the PO Date field: a.
Do not close this process. Continue to Exercise 2. Step 1. Another way to insert a step in the Steps area is to place your cursor in the Steps area and press Insert on your keyboard.
Click the Object drop-down arrow and select Execute. In the Description field, type Executes Process to enter materials information. Certify allows you to cut or copy steps from one process and paste into another process. We often want to isolate steps to populate a table or grid into a child process so that these steps can be fed data from a recordset and the process can be used to input one or more row of data.
To cut the Materials table: a. A dialog box appears asking to save the current process. Right-click Step 11 Materials table. Select Cut. Right-click in the Steps area and select Paste. The step appears in the Steps area. Click the Action drop-down arrow and select Search Empty Row. At the bottom of the screen, in the Parameters tab, in the Row Number field, click the Select Variable button.
In the Variables pane, scroll down the list and select the Row variable. Note: Row will be populated with the row number in the table that the action finds. Instead of scrolling through the list, you can use the Filter field by simply clicking in the field and typing the desired variable name. The Variables pane will automatically scroll to that variable. You can then select the variable from the list. The variable name appears in the field. In the Column 1 Name or Number field, type Material.
For this example, we want to capture the caption of the field because, with tables and grids, columns can get moved around and tables can be customized by the user. By using the name of the column instead of the location number, that will guarantee that we will always have the correct column. Add Step 2 to the process: a. Right-click Step 1 and select Insert Step Below. A new step is created in the Steps area.
The new step contains the values of the previously created step. This saves time when creating steps for the same window or object. Click the Action drop-down arrow and select [Input Cell]. At the bottom of the screen, in the Parameters tab, in the Value field, click the Select Variable button. In the Variables pane, scroll down the list and select the Material variable.
In the Row Number field, click the Select Variable button. In the Column number or caption field, type Material. Add Step 3 to the process: a. Right-click Step 2 and select Insert Step Below. At the bottom of the screen, in the Parameters tab, in the Value field, click the Select Variable button The Select Variable window appears. In the Variables pane, scroll down the list and select the Order Quantity variable. In the Column number or caption field, type Order Quantity. Add Step 4 to the process.
Use LiveTouch to create steps to press the Enter button. Verify that the fields are pre-populated. In Certify, in the Steps area, right-click the last step Step 3. Select the Enter button. A red highlight appears around the button and the information from the object selected appears in the Certify LiveTouch dialog box. In Certify, in the Steps area, right-click the last step Step Select the Save button. Select the Status bar at the bottom of the window. In the Steps area, the two steps are inserted.
Add parameters to Step a. Click Step Click the Action drop-down arrow and select Verify Property. At the bottom of the screen, in the Parameters tab, in the Property field, click the drop down arrow and select Text. In the Criteria field, click the drop-down arrow and select Contains. In the Value field, type has been saved. Add Step 14 to the process: a. Right-click Step 13 and select Copy. Click the Action drop-down arrow and select [Store Parameter]. At the bottom of the screen, in the Parameters tab, in the Index 1 to 8 field, type 2.
The status bar object contains eight index parameters where the SAP developer can store information in those parameters. Typically, we find the key value will usually be found in Index 2, but if it is not there, we oftentimes find it in Index 1. In the Variable field, click the Select Variable button. In the Variables pane, scroll down the list and select the Order Number variable.
Lastly, we will add a screen caption image. This is used to see the results of the steps. Add Step 15 screen caption image to the process: a. Right-click Step 14 and select Insert Step Below. Click the Object drop-down arrow and select Operating System. Click the Action drop-down arrow and select Capture Screen Image. Click the Save From the File menu, select Close to exit the Process Editor. You have completed the steps defining a process in Certify.
You even added variables to a few of the steps. The Configuration dialog box is the starting point for the certification process. It provides options for choosing the type of execution, how and when execution is performed, and how the results are handled.
Configuration consists of setting the run and log settings and providing where to find input data and startup data. Certify allows you to execute the entire process with or without interruptions click Run in the Execution dialog box or you can execute the process step-by-step click Step in the Execution dialog box.
This allows you to see if your process steps are correctly defined and in the correct order for your application. Once you start execution if you are stepping through your process, you can see the log as it progresses through execution, view the stack, review the steps in the process, view variable values during execution, and view recordsets values during execution.
As each process is executed, results are logged and stored in the user-specified folder. The default folder is the top folder. Viewing and Interpreting Execution Results When execution is complete, the Certify Result Viewer opens where you can then review the results of the execution run.
Summary results for the processes are provided in the initial view. You can drill down into the processes and view the step level details. Additional data such as the expected and actual values, recordset data, and test step images may also be reviewed by selecting the corresponding tab. In the Results Viewer, you can view the results of executions, export the results to an. When reviewing and debugging your processes, for any failed step, review all the circumstances to discover any possible causes, such as improper setup or starting state, an incorrect database state, application context issue, an error in the test itself, or another type of error that might explain the failure.
Only when you have ruled out other causes for the error should you conclude that it is a potential defect in the application under test. Execution and Execution Results are covered in depth in Lesson 2. A short-cut menu appears. Click Run. The Configuration dialog box appears. Click Start. The Execution dialog box appears. The process executes and upon completion, the Result Viewer appears.
If it failed, expand the Result Viewer tree to determine in which subprocess es the failure occurred. Drill down until you see the failed step information in the Summary pane. Notice that the Detail pane provides additional information about the failure. When finished reviewing the results, click the red the Result Viewer.
Open the Process Editor and make any needed corrections to the failed steps. Figure 4 — Certify LiveTouch With Certify LiveTouch, you now have the ability to learn objects while adding steps to your process and saving the object to a specific application version. LiveTouch will automatically add the object to your selected application version. You can keep adding steps to your process using LiveTouch without going through the trouble of using SAP Learn to learn the screen.
Exercise 2E is an example of how to use this feature. Certify LiveTouch may cause an error if more than one person learns the same object at the same time. Therefore, your instructor will demonstrate this feature or assign one participant to demonstrate. Do not enable the feature unless instructed. Step Action 7. Verify that SAP is opened to the desire window.
In Certify, in the Navigation pane, click Processes. In the Summary pane, right-click the desired process and select Edit. The Steps tab appears. In this example, a step has already been created that will input the value VA01 into the OK Code field. In the Certify LiveTouch dialog box, click Pause so that you are able to select options from the Learn menu. Click Learn. A drop-down menu appears. Check the Learn Objects if Needed option. Click the Save Objects to Application Version arrow.
Select the desired version from the list. If a version is not specified, you will be prompted after your object selections to specify a version. Click Start to begin creating steps. Select the objects by clicking in the object fields. For this example, the following objects were selected: In the Steps area, a step has been inserted for each selected object and the steps are pre-populated with the application version, window, object, and action.
Notice a variable was created for each object. It will not work with SAP single sign-on. If you have set up your environment for SAP single sign-on, it is recommended that you add a service user to SAP in order to allow for Capture Process to function. As shown in Figure 5, you must have a SAP session open for the feature to work.
You then navigate through the SAP application, capturing your objects to create your process. When complete, you simply log off SAP. The Import Completed Successfully dialog box appears.
Click OK and open the process in Certify to review or edit the steps. You can then run the process to verify the steps work properly. Verify that you have a SAP session open. Right-click in the Summary pane. A Short-cut menu appears. Click Capture Process. Select the Enter Click the Exit button. The new process is added to Certify with all the steps that were performed.
In the Processes pane, double-click the Test process. The Process Editor window appears. The steps you performed in SAP appears. As shown in Figure 1, the Configuration dialog box provides options for choosing the type of execution, how and when execution is performed, and how the results are handled.
If you want your execution to stop when a failure is encountered in your process, select this check box. Failure includes failed and aborted steps. Modes include managed, manual, and unmanaged. Managed mode allows user intervention to step through processes, set breakpoints, and capture screens. Managed mode assists you in debugging your processes. Manual mode is required when an application is not being run or not developed , and you have no automation or the automation is not working.
If your mode is Manual, the Execution dialog box will have an additional tab called Manual Execution. Unmanaged mode prevents you from stepping through execution, setting breakpoints, and capturing screens. Step delay helps resolve timing issues when testing your application. When you determine your process is complete, you can log aborted or failed steps only. The WindowChange option is helpful when you want to see the window or object that is failing in your application.
It is also good for a final result, giving you a screenshot after every window change. The Select Results Folder dialog box allows you to select any project for which you have permissions. The default is the current directory that holds all information for the opened project. The default is the current layout associated with the process. If blank, no layout is associated with this process. If you choose a layout and do not choose a recordset, the layout is ignored during execution.
To delete a selected layout, click the 76 button. Select the down arrow to choose the recordset you want to use. Select the down arrow to choose the mode for the selected recordset. Table 1 below explains when and how each mode is executed. Loops process once for each row until End of File. Append Writes recordsets at the end of execution. Appends to existing recordset and loops process until Abort or Exit. Clear and Append Writes recordsets at the end of execution.
Creates new recordset for each execution session and loops process until Exit. Read and Update Reads recordsets at the beginning of execution. Updates the recordset at the end of the process.
Insert checkmarks for any or all of the application versions to be checked for context. By default, there is no checkmark, meaning that the process will run. If the box is checked then the process will not run. The application version will have the name of the State process if one has been created and selected in the project. If you do not check any application versions and have a defined start process, the start process loads the application, performs log into the system, and navigates tot the main window or starting state before starting execution of the process.
Set the fields with values before executing so the values are stored with the results. No changes are saved. Execution Once you click Start on the Configuration dialog box, the Execution dialog box appears as shown in Figure 2 below. After execution, the Result Viewer dialog box appears shown in Figure 3. Once configuration is complete, you can set additional execution functionality in the Execution dialog box, such as skipping process steps, capturing application windows, and setting breakpoints.
Figure 2 — Execution Dialog Box Execution Buttons The following Execution buttons offer you different options when running your processes. If the step is an Execute Process step, then the execution moves to the first step of the called process. Skip — Skips a step during execution of the process. If the current step is an Execute Process, then the process will not be executed.
Text will be marked aborted by the user. This option is helpful when you want to see the window or object that is failing in y our application. Execution Dialog Box Tabs The following Execution tabs offer you different views when debugging your process execution.
The Expand view allows you to view the steps while using the other tabs. Watched variables are persistent throughout execution. The Process tab shows local variables. Nested calls are indented. Processes are shown in the order they have been executed. By now you have seen the Result Viewer many times. Once you close the Result Viewer it is stored and managed in the Results window, which is accessible from the Certify Navigation taskbar. You can keep only process summary information or both process summary and failed step information.
In the Details pane, you can view the details for a selected result and view the values any user-defined attributes associated with the results. Viewing Execution Results The Result Viewer allows you to expand the execution results to show each process and step executed.
The Navigation tree displays a log header with details about the process you executed. Under the log header is a hierarchy of processes executed. You can expand each level of the hierarchy and view information about the executed processes and steps in the Summary pane. Processes in the Summary pane display information about test status, elapsed time, start time, end time, and who created and modified the process. The Detail pane displays additional information about the process and any associated recordset values that were used by the process.
Figure 4 — Result Viewer Steps in the Summary pane display information about test status, elapsed time, start time, end time, as well as the components of the step. The Detail pane provides additional information about the executed Certify 8. Table 2 lists the statuses shown for the executed processes. Table 2 — Executed Process Status Status Description Passed step or process Skipped step or process Failed step or process Aborted step or process Table 3 lists the statuses shown for the executed processes.
In some cases, a process inherits a status based on the status of another process or step. The Process and Data Editor window opens to the step you selected.
From here, you can modify the step and run the test process again. From here you can run a report that shows a summary of the selected results from the process level or details of the results including step components, as well as a recordsets report that displays only steps with values of the selected results. The execution reports are displayed in.
As shown in Figure 5, the report shows the results in the same order they are displayed in the Results Viewer order of execution. Figure 5 — Sample Execution Report Certify 8. On the Navigation taskbar, click Results.
In the Summary pane, right-click the desired process and select Reports. Select Results Summary. The Choose a location… window appears. Choose a location to save the report.
In the File Name field, type the desired name for the report. Click Save. The report opens in. Mastering this concept is the first step in understanding data-driven testing.
In Certify, variables are an important component of the Business Process Certification because they provide a means of representing the data that you want to use in your processes.
The most common use of variables is for data-driven testing, where process execution loops through a series of data values.
Variables can also be used when you need to store or verify system data, such as the System Date or Machine Name, or when specific data for a user is required, such as a user ID or password to log into an external system or application. Preparing to use Variables When preparing to use variables, the first thing you should do is go through your existing processes and identify all the places where variables can be used in place of static data.
As a best practice, create a table or spreadsheet showing the processes and all of the variables that you will use for each process. This method will help you later when you create the recordsets to be used with your processes. Project variables can be created and managed in the Variables window or while creating processes in the Process Editor. You can use Project variables on both the Data window to define the layouts of your recordset and on the Process Editor to hold the values of objects within your process steps.
Since Process variables are only available to s specific process, the variable names only have to be unique to that process. Solutions Ensure your success with comprehensive solutions spanning all three stages of automation—discovery, testing, RPA—in one codeless platform.
End-to-End Testing Run end-to-end business process tests for packaged applications with enterprise level controls and reporting. Web Testing Simplify the complexity of web challenges by testing automatically as updates to web applications as they are released.
Cloud Testing Cloud testing allows you to run a huge number of tests in parallel, both locally and remotely, facilitating easier and larger-scale deployments.
Mobile Testing Reuse tests, no matter which mobile platform is used, and maintain one test for multiple browsers and devices. Exploratory Testing Extend the power of exploratory testing by automating the discovery and documentation of as-is business processes.
SuccessFactors Business process assurance for your end-to-end HR processes. Concur Ensure quality: test every workflow. Hybris High-speed functional testing for digital commerce.
Ariba Ensure crisp execution in eCommerce. Fiori Ensure the highest-quality user experience. PeopleSoft Keep pace with system changes and drive agility. Siebel Ensure quality and high levels of execution end-to-end. JD Edwards Handle complexity and mitigate risk for your application modules. Salesforce Ensure every CRM and customer-focused function works the way you need it with automated salesforce testing of end-to-end business processes. SuccessFactors Our industry-leading automation is designed to validate end-to-end processes, delivering higher levels of QA across applications, technologies, and interfaces.
Industry Spotlight Explore real-world success stories from customers by industry. Partners Experience the power of a best-of-breed technology ecosystem with deep expertise Request Partner Licenses Demonstrate Worksoft's connective automation to your clients by requesting proof of concept POC , pilot or project licenses.
Access Partner Training Courses Access all of our latest training courses to anything and everything Worksoft and our suite of products and solutions. Support We're dedicated to the success of your organization. Take a look at our full list of support options and we'll do our best to assist.
Customer Portal. Drastically reduce testing time without sacrificing quality. We are now reducing the effort vs. Validate complex processes in a fraction of the time of manual testing. Create, manage and execute functional testing across applications and technologies with codeless automation. From ERP to web and beyond, our test automation spans every application your business processes traverse. Our test automation framework uses object definitions that empower you to keep pace with change without updating individual test scripts.
Reusable automation assets let you build and share automation across scripts, projects, and teams. Drive efficiency and increase quality to experience tangible business benefits in the form of time, cost and resource savings.
A shorter cycle test that took an hour before, now takes a few minutes.
0コメント