Sunday, November 7, 2010

FAQs on Autoczar Object Identifications, Synchronization and Recovery Scenarios

This article puts lights on few Automation FAQs mentioned below which were asked by our esteemed customers

  1. What are the different objects identified by Autoczar?
  2. How to do objects synchronization in Autoczar?
  3. How to work with recovery scenarios in Autoczar?

1. What are the different objects identified by Autoczar?

Below are supported platforms\application supported environments whose objects are identified by AutoCzar with build V10.2. Autoczar differs how effectively and efficiently it supports each platform in real scenarios with compare to other automation tools like QTP\Silk Test. Have a look to my up-coming article SAP automation support on AutoCzar with compare to QTP or Silk Test for more detail.

  • Web
  • Oracle E-Business Suite.
  • People Soft.
  • AJAX, i-Frames, JSP, ASP, HTML and web 2.0 related technologies.
  • .Net 2.0 Applications.
  • Java\AWT applications.
  • Supports IE 5.5 and above & Firefox 3.0 and above.
  • Adobe Flex\ Air.
  • Flash.
  • WPF.
  • Silver Light.
  • SAP.
  • Web Services.
  • Windows - NT, 7, XP, Vista 32-bit and 64- bit support.

Autoczar support team has helped clients and extended above list of supported platforms\environments on their needs. For more details download Autoczar from here and look into the help.


2. How to do objects synchronization in Autoczar?

Autoczar gives opportunities to synchronize objects statically as well as dynamically.

Type of Synchronization

Keyword

Purpose

Static

Wait

User can let Autoczar test-step execution wait statically.

Dynamic

WaitForApplication

User can let Autoczar test-step execution wait dynamically for application exists.
For example, If Use has test-case which launches application under test and performs test. In such scenarios, He\She can draw test-step with this Keyword.

WaitForObjectProperty

User can let Autoczar test-step execution wait dynamically for specific object property exists
For Example,
If User has test-case which submits valid data inputs; While filling inputs in form, AUT dynamically checks for valid or invalid inputs based on this background validation, AUT makes Button: Submit enable or disable.
He\She can use Keyword: WaitForObjectProperty along with expected property(enable\disable) to wait before click on Submit button.

Customized

Customized keyword

User can create its own keyword and integrates with Autoczar for custom synchronization as per the needs.


Dynamic Synchronization in sample test-steps

Action

Field Screen

Input

Expected

OpenApplication


AUT url


WaitForApplication

MainAUTWindowObject

10


Input

FormEditboxObject1

Some inputs


Input

FormEditboxObject2

Some inputs


Input

FormEditboxObject3

Some inputs


WaitForObjectProperty

SubmitButtonObject

enabled,true,8


Click

SubmitButtonObject



It will open application under test and wait for AUT MainWindow appears until 10 seconds then it will fill the inputs and wait for Submit button gets enable until 8 sec to click button.

3. How to work with Recovery Scenarios in Autoczar?

Autoczar has an Exception Handling. User can create steps to handle while exception raised and associate exceptions to one or many test-suites. For Example, I have test-cases which Log In to shopping web site and purchase few items. In few web-pages, IE pops up with security message like




To handle such pops up, one can create steps in exception handle and associate them to the test-suite so Autoczar will handle such unexpected pops-up dialog-box while test-cases are executing.

With Regards,
Nimesh.

No comments:

Post a Comment