Demo : Automate a typical web test-scenarios with Autoczar

Demo explains how to automate a typical web test-scenarios “money transfer” on mybanco with Autoczar.



Please, feel free to comments for any details.

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 U-Turns for Test-Engineers

Developing automation test-scripts(Test-Case) is a kind of art which under takes by our best of the best automation test-engineers in organization’s testing team. We all know that automation test-scripts should be independent entity which carries many characteristics such as re-usability, de- factorized , less redundancy blab la bla. But what happens when our automation Test-Engineers implement test-scripts in real-time?

Aren’t they facing any challenge while implementing automation Test-Case(s)?

Of course, As we all know - they have challenges; In this article, I want to take a look on few common challenges that our Test-Engineers are facing everyday while making automation scripts and focus light on their resolutions with Autoczar.

Hey , My automation Test Case is not running – I can’t move a bit ; don’t know what to do?

Here, root-causes may vary on one test-scenarios to another test-scenarios but few of the common mistakes are such as
#1. Input arguments to execute on AUT’s objects are not valid.
#2. Step is missing which initiate to further steps to execute.
#3. Steps are invalid (may be they are not in correct order or steps are not correct with actions and object pass to execute on)

He \ She can resolve these typical issues with leading automation testing tools by following one of the approach
#1. Execute all steps and based on output log; he/she can correct inputs/step(s).
#2. Execute Test-Case step by step and based on output log; he/she can correct inputs/step like debugging automation steps.
#3. Analyze test-case(s) invalid inputs manually.

Approach #1 and #2 is better than approach #3 (Obviously, Manual interruption will take more time and again it is an error prone). Test-Engineer may not resolve all issues with approach #1 also because Test-Case(s) invalid inputs\steps may cause blocker to execute further steps and he/she needs to take approach #2 (debugging steps one by one) at last.

For Modular Automation Framework, to re-execute Test-Case(s) step by step in debugging mode may become headache and reaching dead-lines become the part of Test-Engineer’s worst nightmares.

Like other leading automation tools, Autoczar also provides de-bugging facility to Test-Engineers.

Unlike other leading automation tools available in market, Autoczar gives de-bugging utility on Hybrid Automation Framework (Keyword + Data Driven Framework) which helps to put very less efforts to resolve issue in debugging.

Autoczar also provides pre-execution validation utility. Autoczar’s one click “Validate” feature helps to validate Test-Case(s) before execution and that cuts Test-Engineer’s efforts to go back and forth while debugging to find invalid inputs in Test-Case(s).

Thus, continuous easy growth (no U-Turns) happens while implementing automation Test-Case(s) with Autoczar for Test-Engineers.

AutoCzar comparison with other tools in a nutshell

Comparing AutoCzar with other test automation tools:

While some of the famous automation tools are the market leaders by revenue, they have not enhanced the cause of test automation. For instance these tools have strong market penetration and have market share of up to 80%. So, why has test automation, in general, had a failure rate of 85% (according to reports)? is the company more concerned about making money than truly helping organizations to build successful, long-lasting test automation envirnoments?

To compare AutoCzar with other tools, let me give an example: The popular automation tools are like CLI type operating systems (ex; Main Frames, UNIX, BSD) which requires highly skilled technical engineers to work on them or to build applications on these OS, these Engineers have to be trained for years to work on them. AutoCzar is like GUI based Operating system (ex: Windows, Linux or Apple), you don’t need trained professionals nor computer experts to perform your job.

The target users being the testers or business analysts, we can’t expect these community to be programmers. 

Looking at the history of these tools, these tools have originated and evolved from a developer’s desk, you can always see a developers perspective rather than a business analyst’s or a tester's perspective. Due to which the testing community makes the necessary adjustments to make the automation program successful, which is time consuming and end up in spending more. AutoCzar is one such tool which is architected, designed and built by pure testing community.

For more comparison, contact us.

Automated quality simplified by Autoczar

According to Oxford dictionary “Simplified” means

• Made a way that is easy to understand or
• Made a way that is natural and plain

Let’s find how Autoczar can simplify automation tasks to achieve quality.

Test case creation is a piece of cake in AutoCzar™

AutoCzar™ has a “Designer” module which provides the record/play utility similar like automation tool QTP,SilkTest,WinRunner and other popular tools then what does Autoczar make "a way that is easy to understand" comparing to other tools?

Let's create a testcase that verifies google result on search key : TestingCzars

Manual Steps to automate would be as
1. Open Browser with URL www.google.com.
2. Input "TestingCzars" to search.
3. Click on button "Google Search"
4. Verify text "TestingCzars Software Solutions" on result page.

To automate above steps, AutoCzar™ has a utility "TC Generator" to record user actions. Autoczar uses keyword/data driven framework which generates steps so transparent that Business Analyst or novice Manual tester even can understand and use them with ease.

Automated steps by Autoczar are as

Action	Object	Input	Expected	Comment
OpenBrowser	Google	http://www.google.com/		Opens Browser for goolge.com
Input	q	TestingCzars		Enter "TestingCzars" to search.
Click	BtnG			Click on Button : Google Search
VerifyText	TestingCzarsSoftware		TestingCzars	Verify result page has "TestingCzars Software Solutions" text link.

AutoCzar™ supports all kind of Microsoft, Java, Oracle ERP, Mobile and multi-lingual applications with novel script-free technology. Automated test-case(s) in Autoczar are transparent regardless of technology under used for application development which raises high productivity and less training require for resources.

Test-case(s) are well organized with Test-Suite in AutoCzar™

AutoCzar™ has an “Executor” module which helps user to organize complex and bulky test-cases to create Test-Suites. User can re-use Test-Suites for different kind of testing like smoke, integration, system, acceptance & regression testing.

Effective feedback loops are possible.

AutoCzar™ has a “Creator” module which helps to define requirements. "Executor" gives opportunities to run your testcase(s) based on requirements. User can associate requirement(s) to test-case(s) and he/she can effectively trace them through out any phase of SDL (Software Development Life Cycle) in agile and V model quality process of the organization.

Taking quality decisions are no more complex.

AutoCzar™ has a "Reporter" module which can generate informative reports to managers, lead engineers, business analysts, clients and owner of the projects on a risk-basked go/no-go decision for release. AutoCzar™ generates reports in four flavors.

1. Summary Report
2. Module Report
3. Test Case Report
4. Test Step Report

Please, free to ask any questions regarding AutoCzar™.
With Regards,
Nimesh.