Automation Testing

for this you can use isequalbin method..i am showing below

' Code for comparing two images

Set CompareUtil = CreateObject("Mercury.FileCompare")

IsEqualFlag = CompareUtil.IsEqualBin(Img1, Img2, 0, 1)

in above code 0 means in file compare class showing no

error ; syntax FC_NO_ERROR = 0

1 means in file compare class showing difference of

size; FC_DIFF_SIZE = 1

1) Write the Test script

2) Run the Test Script

3) And make a Report

option Explicit

Dim Str, i, arr_len

Dim arr(10)

arr(0)="I"

arr(1)="N"

arr(2)="D"

arr(3)="I"

arr(4)="A"

arr_len=Ubound(arr)

for i=0 to arr_len

Str=str&arr(i)

next

msgbox Str

Browser("Browser").Page("Page").Webobject("PropertyName:=Property

value").GetRo("Property")

Normal identification--HTML TAG,Name and Innertext in case

of webelement or link .If that is not enough for

identification will go for assistive itdentification items

and if not able to recognize then after it will use ordinal

identification like index location creation time in case of

web Browser.

In iterative model, the requirements are given in advance to the tester based on which he can prepare test cases.Using the test cases, the developer can prepare the required source code accordingly.This method is also known as Test Driven Development.(TDD)

Testing is the process of finding bugs,defects or error.or

it is simply checking whether the software/application is

matching with the SRS or not.It is done by testers.

Debugging is fixing of bugs.It is done by developers.

Development is the process to write the source code for a given program for a specific application. It is done by developers.

Testing ,on the other hand is to test the application with the intention of finding errors/ defects in it. It is done by Test Engineers.

-Quality means only and only "meeting specification" nothing

else.

-what a user want??if he is getting everything then he will

say good quality.

-Quality leads to a brand not the vice verse.

-Testing doesn't mean quality improvement.

-Testing means exercising your brain a little bit to

examine a product..In turn the result is improvement of

quality.

SO QUALITY IS NOT THE AIM OF TESTING,BUT OUTPUT LEADS TO

IMPROVEMENT.

A tester generally does the following task in ETL environment:

1. Review the requirements

2. Review the source data - data profiling.

3. Modify the source data to meet any requirements that

weren't already met with the original source data.

4. Execute the ETL job(s)/transformation(s).

5. Validate the results.

6. Validate that the data is usable. If the data isn't

usable, then you really haven't gained anything.