Best ways to use Certify Process Capture to create test automation requirements


Clear and concise requirements are always the cornerstone for the success of a Test Automation Project. Traditionally, the automation team is provided the requirements in the form of a shared folder in a Test Management Tool or spread sheet or recordings. It’s often observed that when test cases are not documented properly and if test data provided is not working, automation team finds it difficult to automate an end to end functionality.

In one of our recent Certify Automation Project, the customer used “Certify Process Capture” for documenting the requirements with great success. “Certify Process Capture” from Worksoft helps the business users record a business process by simply navigating through the business process as part of their regular task. The test automation team imports these XML files and create Certify Processes which are later enhanced to work as end to end processes. Certify Capture creates steps for all user interactions with Applications under Test (AUT) and it supports SAP GUI, HTML, and Mobile Apps.

Before initiating the development of End-to-End process, the team executes the “Certify Capture” steps ‘as-is’ to understand the functional flow and to validate completeness of Capture steps provided as requirement. “Certify Capture” steps include Application Version Name, Window, Object name and Actions performed on each object. Test Step Images are also captured which show up as object image with Master Data entered.

Here goes some of the best practices followed by the Business Users in this project which contributed immensely to the success of the automation project

  • “Certify Capture” was used in a controlled environment. Only AUT for that specific business process were open while capturing steps and all the other windows were closed.
  • Business User kept all the Master Data ready before initiating Certify Capture session. Wherever possible they used data which would run for multiple iteration.
  • Comment lines were used generously by the Business Users. This improved readability and documentation. Comment steps were used to mention all the validations and business logic that were supposed to be validated in the end to end testing.
  • There were few sensitive objects like Menu selections, Table, Grid, System Objects, and ActiveX Controls which were often not captured properly. In such instances, the Business users added a comment line before inserting those action steps.
  • Master Data details were added in a comment before using them in the action step.
  • Certify Process Capture ability to take screen capture was used to document any critical validations.
  • Business Users used a well-defined naming convention while saving the process.
    Contact SOAIS to know more on how you could benefit from our best practice experiences with global customers.

    Contribution by Saravana Kumar

LEAVE A COMMENT