combined project

CHRISTOPHER SVEDA

Test Automation Engineer Intern Quality Assurance

Summer 2015

Table of Contents

HP Unified Functional Testing Intro ............................................................................................................. 1

CCB Baseline Test ......................................................................................................................................... 3

CCB Baseline Script ............................................................................................................................... 4

MDM Baseline Test ...................................................................................................................................... 5

MDM Baseline Script............................................................................................................................. 6

CCB Configuration Test................................................................................................................................. 7

CCB Configuration Script ....................................................................................................................... 8

MDM Configuration Test.............................................................................................................................. 9

MDM Configuration Script .................................................................................................................. 10

MDM – CCB Sync Test ................................................................................................................................ 11

MDM-CCB Sync Script ......................................................................................................................... 12

CCB Comprehensive Rate Check Test ........................................................................................................ 13

CCB Comprehensive Rate Check Script ............................................................................................... 14

Desktop Integration Testing – Tier 1 ......................................................................................................... 15

Windows 7 Tier 1 & 2 Scripts .............................................................................................................. 16

CCB – Create Account Test ......................................................................................................................... 17

CCB – Create Account Script ............................................................................................................... 18

CCB Create Person, Account & Service Agreement Test ........................................................................... 19

CCB Create Person, Account & Service Agreement Script .................................................................. 20

OUA Baseline Test ...................................................................................................................................... 21

OUA Baseline Script ............................................................................................................................ 22

Other Created Tests ................................................................................................................................... 23

HP Unified Functional Testing Intro

Purpose / Importance

An effective automation tool that saves testing time and effort.

Automation is used mainly to compare the actual outcomes with predicted outcomes.

This tool allows an option for users to create either an API or GUI test.

UFT is user-friendly program that provides versatility between click-and-script via the

recording function and manual VBscript coding.

Through simplicity, users would be able to debug their tests during the test, review results

upon the completion of the run, and export their results if desired.

Since UFT and Excel both work with Visual Basic, the compatibility easily allows for the

importation/exportation of data from cells, worksheets or workbooks.

The left panel normally will

display the solution or toolbox.

This allows users to change

action names, view actions in

details and if repository items

were included. This could be

collapsed for a bigger

workspace for coding.

This is workspace for viewing

actions, recording/manual code,

and data tables (on a lower

window). Double clicking any

action will display the code

within.

Properties would normally

be displayed at default, and

it displays the test or action

settings and if there were

parameters established.

Record – Allow user to configure the

sensitivity of the mouse / clicking. Also,

includes the ability to record from

existing or new window.

ALM - Connect with the ALM

Server to export or import tests.

This button would allow for

exporting defects as well.

Toggle Switch – Allows user to

switch between code keyword

view and editor. This is essential

when debugging or adding

parameters to the data table.

Solution Explorer – Allows

user to view a more detailed

panel regarding the actions /

repositories listed. Changing the

action name could be done here.

Toolbox – Allows user to

access user-set customized

tools or application tools that

are available.

Properties – Shows user details

of the project, modifications,

parameters that are used in the

project/action.

Debug Panes – User would be

able to set breakpoints, local

variables and use the console for

debugging purposes.

Object Spy – Used to capture

objects, windows or any other

fields. You may be able to copy

it to the clipboard or to the

repository.

Object Repository – A tool that

stores all of the objects. You

could obtain them from the spy

or by clicking the plus symbol

on the repository toolbar.

Run Results – This tool shows

the end results of passed or

failed checkpoints, actions, etc.

This could be exported to html

or doc files for reference.

Data – Allows user to view/edit

the data table. This works with

parameterization and the amount

of iterations the test is set up for.

CCB Baseline Test


To test basic functionalities and provide verification in the CCB environment.

The baseline, also known as a smoke test, is to provide non-transactional events.

This is also to ensure that the environment is still operational after patches, updates, etc.

Biggest Challenge

This started out as an introductory test,

so understanding how the tool works in

conjunction with the web-based

program did impose an initial

challenge.

Favorite Part

While learning the basic functionalities,

I eventually figured out how to

recognize system windows with the

tool and was able to print.

What I Learned

Using Systemutil.run as opposed to

UFT automatically launching the URL

since it became problematic.

Despite the automation process, some

events call for the “Wait” command.

Object Repository / Object Spy.

Debugging errors during the test.

Using the toggle switch for

accessibility to create parameters.

Creating parameters for the users and

passwords.

What is included?

MDM Baseline Test


To test basic functionalities and provide verification in the MDM environment.

The baseline, also known as a smoke test, provides repetitive non-transactional events.

This is also to ensure that the environment is still operational after patches, updates, etc.

Biggest Challenge

Understanding the Scalar consumption

aspect on CCB imposed a small issue.

Having no prior knowledge of the

subject creates a difficulty when

creating a test for this field.

Favorite Part

Aside from the printing (which I am

fascinated by), the inclusion of

checkpoints were interesting because of

the versatility it presents. There are

multiple checkpoints you can create,

such as area, output, standard, text, etc.

Additionally, you could pull out what

you would like to checkpoint within the

type of checkpoint, such as innertext,

html, value, etc.

What I learned

Changing the sensitivity of the mouse

capture and understanding how the

FireEvent command works.

Understanding the window properties

in detail, and what exactly is being

captured.

What is included?

CCB Configuration Test


To ensure functionality is operational in the CCB environment after each deployment of

new code, patch or updates.

The versatility of running the test in multiple environments allow for maximized

visibility of comparison between the two environments.

Biggest Challenge

Understanding how environments and

iterations worked and how to set them

in order to run during specific times.

Favorite Part

Despite the other tests that I created,

this would have to atop the list. Being

able to implement something in the

developer environment and testing it in

another is extremely interesting. In

better context, when I create something

in the developer environment, it should

pass and in the normal environment, it

should fail. Once the developers deploy

the configuration changes (usually over

the weekend), it then should work on

all environments after.

What I Learned

How environments and iterations work.

The CreateObjects command via Shell.

If Statements w/ Inputbox commands.

String Command with variables.

What is included?

MDM Configuration Test


To ensure functionality is operational in the MDM environment after each deployment of

new code, patch or updates.

The versatility of running the test in multiple environments allow for maximized

visibility of comparison between the two environments.

Biggest Challenge

Often the new code is deployed, older

parts in my test would fail and having

to find and fix the issue(s) became

problematic.

Favorite Part

Viewing the device configurations on

the gold environment and how they

transpired to the IT2 environment upon

deployment was interesting. Being able

to view their changes in near real-time

is fascinating and I believe that

automation could be used with the

developers to test their work prior to

deployment.

What I Learned

Transactional Checkpoints.

How to run multiple iterations.

Ability to toggle the sensitivity of the

actions during recording as opposed to

stopping and changing.

What is included?

MDM - CCB Sync Test


To ensure that the link between MDM and CCB is operational.

Could be used after each set of code that deploys to make sure that connectivity is still

present.

If there is no connectivity between the two programs, not only would you be unable to

perform transactions, but it impacts data to bill customers, acquire meter and weather

data, etc.

Biggest Challenge

I believe my only challenge was

figuring out what to change on the

person’s account on CCB that impacted

the link for their information on MDM.

Favorite Part

Being able to perform a transaction in

between two environments to ensure

that they talk in near real-time was

exciting to see. However, if the test

does not update then it’s clear to say

that the link between the environments

are broken. This is an essential

component because there are many

components that rely on the

connectivity.

What I Learned

Creating a real-time transaction.

Able to change an item in one

environment and watch the change into

another environment in real time.

The utilization of the Data Table within

HP UFT.

What is included?

CCB Comprehensive Rate Check Test


To ensure that the results produced with the appropriate rates match the results that are

produced in CCB with the same rates.

Over time, rates change as well as their respective peak, seasonal and tier level rates. So,

this test assures that the values correlate between the two systems.

Biggest Challenge

HP UFT recognized all of the fields

except for the exact one I needed,

giving me a false value. This value was

needed to be retrieved for comparison,

so a work around had to be

implemented.

Favorite Part

Using the excel sheets without having

to have them open during the test was

beneficial. When the excel sheets were

called during the test, they would

disrupt the work flow and also the user

would eventually have to close them,

which could become tedious.

What I Learned

DataTable.Importsheet(s)

Excel Data Retrieval

Excel Data Check (Open = False)

Excel Cell Values (Import/Export)

Length Command

Variable numeric signs

ExitTest Command

SendKeys Command – Shell

What is included?

Desktop Integration Test


To ensure that the appropriate settings, applications and functionalities are set for test

users or users after updates / patches.

Making sure that the appropriate icons are located where they need to be and to have the

correct settings / user controls.

Biggest Challenge

HP UFT does not recognize any of the

window functions outside of web-based

programs or applications. Frustration

started to build because of the fact that I

was annoyed of the automation tool

being so limited. However, after some

research I was able to improvise the

clicking aspect with keyboard

functions.

Favorite Part

Since up this point, majority of the tests

were click and script; however this was

entire new ball game. Being able to use

the keyboard strokes to launch

application or to navigate within the

windows directories was definitely an

accomplishment.

What I Learned

Keyboard Commands using the

SendKeys method via Shell.

Press and Activate Commands.

MicRightBtn command to capture right

clicks.

Understanding that the inclusions of

wait commands are essential when

using the SendKeys command.

Capturing screen and window

recognitions.

What is included?

CCB Create Account Test


To create multiple accounts through iterations from a database.

Having the user to be able to import an excel sheet and produce the account information

in repetition during the test.

Allowing the test to run without logging in and out to conserve some time.

Biggest Challenge

Configuring the iterations for logging

out. Being able to set the initial

iteration was not an issue, but the

logging out was contingent upon the

amount of accounts that were created.

Favorite Part

The aftermath of the test and visually

seeing the amount of accounts that was

created on a single user. The repetition

aspect was very handy in this case

because this saves quite a bit of time

from doing this manually.

What I Learned

Incorporating If statements in specific

Environments depending on what the

action required.

Allowing to login once then creating

accounts upon repetition.

FireEvent Commands “onmouseclick”

and “ondblclick”.

Understanding of excel commands on

UFT such as, save, close, false and true

for being visible.

Calling the data validation on Excel

from a separate sheet.

What is included?

CCB Create Person, Account and Service Agreement Test


To create the left side of the “V.” This includes creating a person and an account with a

service agreement associated to their account.

This saves a great deal of effort and time by inputting the information into an excel sheet

as opposed to doing this manually. Additionally, confusion could occur on what was

done previously; however, by the implementation of importing the excel sheet, you’re

able to keep track of what is being done.

Biggest Challenge

Understanding the types of Service

Agreements and what was compatible

to produce an outcome. I had to refer to

experts in order to find the correct

specifications to complete this test.

Favorite Part

Creating the non-premise service

agreement was tedious, but enjoyable.

The action called for roughly 345 lines

with over 30 IF / Else IF statements.

What I Learned

Correlated a comprehensive excel

spreadsheet with the UFT parameters

using import datatable

Created half of the “V” while getting a

better understanding of how everything

all ties together

Allowing the test to refer to a specific

cell in an excel datatable and having the

outcome of that cell perform an action

on UFT.

What is included?

OUA Baseline Test


To ensure that functionality is present since this is a relatively new product that will be

utilized in the future.

Testing each field and link, including viewing graphs and generating reports.

Biggest Challenge

With this being a new product, lots of

functionality was yet to be deployed.

Additionally, there were a limited

amount of experts in this program so it

was to anyone’s guess of where to

navigate and what produces what.

Favorite Part

Being able to navigate through a new

product and veering off from the usual

web-based systems I was using.

What I Learned

UFT recording configurations do not

need to be adjusted on all web-based

programs.

The functions of the new program and

how they are affiliated with the current

project.

What is included?

Other Created Tests

Parameter / Iteration Test

Tested users, passwords, and search names through multiple iterations and parameters for

flexibility for the user.

Multiple URL Test

To test URLs were successfully launched from inputbox end-user responses in conjunction with

the systemutil.run command.

Excel Retrieval Test

This test called for multiple values in various excel sheets and utilized them to export in tests for

either the web-based program or to another excel sheet.

SOAP Test

To launch the SOAP (Simple Object Access Protocol) application and to run the weather tests to

retrieve various information from KBFI and KSEA.

Data Import Test

To store and use the information from an excel sheet and the data table in the UFT application.

Customer / Exception / Revenue / Credit Collections Analytics Test

Since the OUA web-based program had quite a bit of functionalities to test, these were

subdirectories that were also tested and explored.

Create Person Test

This was used in addition to the massive ‘Create Person, Account and SA’ test; however this was

the initial test to simply create a person by filling in all the required information.

Field Activity Sync Test

To test the Field Activity aspect to see if it populates, similar to the CCB-MDM sync test.

Desktop Integration Testing - Tier 2

A test to verify that other applications such as Outlook, Office, Adobe, and Novell Client are

operational.

Regression / Portal Regression Test

A test to verify that the customized portals work correctly as well as previous configurations.

combined project

Documents