MSCCT32 Automation – Keywords Approach

healthyapricotΜηχανική

5 Νοε 2013 (πριν από 4 χρόνια και 1 μήνα)

108 εμφανίσεις

1.
Introduction
-

Objectives

2.
Introduction to Automation

1.
Manual vs automation testing

2.
Main Advantages

3.
Limitations

4.
Introduction


Design Approach

3.
Automation Tool


TestComplete

1.
Introduction

2.
Licenses

3.
TestComplete IDE

4.
TestExecute

4.
MSCCT32 Automation

1.
System
Requirements

2.
Dependencies

3.
Architecture

4.
Keywords Approach

5.
Store


6.
Data Generator

7.
Areas of Use

4.
List
of Keywords

4.
Standard

5.
Positive

6.
Branch &
Condition

5.
Exclusions

6.
Creating Scenarios

1.
Installer

2.
Creating Project

3.
Creating Keyword Tests

4.
Execution

5.
Reports

7.
Demo Scenarios & Hands On


Automate
functional
tests for
Masterscope


(Standard features
as well as study
-
specific workflows)

Reduce
Testing Time

(Adaptable with
new studies &
tests reducing lead
time for delivery)

Generate Bulk
Data

(From MasterScope
systems for
Expert3)

Future
-
proof
Investment

-

Extendable for
new modalities
(plug
-
ins), New
release of
Masterscope ,
Device in
Hardware Mode


Manual Tests

Automated Tests

High

Effort and Cost
requirements

Low Effort

and Cost
requirements

Time consuming

Quick; allows test engineers
to focus on

functional areas

Tests are not reusable

Complete reusability

based
on type of implementation

Mostly used for integration
tests

Can be used for any tests
including load, sanity,
system, etc

Risk of

human errors

Script validates all areas once
tested

Reduce time
-
to
-
market for studies

Improve consistency and reliability of tests

Manual testers do more complex workflow validations and
use functional expertise to use automation

Automation provides measurability of tests and can enforce
SLAs

Increased test coverage for each cycle per build

Complex to develop


Development is already done and tested

Maintenance of test data files a big challenge


This solution generates test data on
-
the
-
run as pre requirements

Automation Script Errors can spoil testing


Continuous validation by functional experts at Vinculum and ERT have
ensured that correct tests are being executed correctly

Scope Changes in AUT difficult to adapt


AUT (MSCCT32) team and automation team work in close interaction to
avoid such challenges

Proficiency required to use automation


Completely UI driven solution created with proper training support

Generic
Framework

Automation adapts itself as per the workflows in a
particular study

Keywords &
Data Based
Solution

-

requires no programming knowledge for end users

-

Data is generated dynamically or taken externally

Portability

of keywords/projects allows for a structured
implementation

Output
reports

Reports are provided for all test runs with
screenshots

Functional automation of windows and web
applications

Recording and playback as elementary support
from tool

This solution is a framework written above it

Keyword driven approach for easy usage

Allows to create portable and reusable test
scenarios

Licenses

Node locked
:

-

run on specific
machines

-

limited usage

-

no flexibility

Floating
:

-

License server

-

limited to
concurrent usage

-

complete flexibility


TestComplete IDE

Headless version


has
no UI

Capable of executing all
scripts created in TC

Supports portability of
scripts

Allows for distributing
creation and execution
of test scripts

Test Execute


MSCCT32 Laptop with 2 GB RAM


LAN Connection for license


Open System


Validation Mode


Dummy Mode


Authentication Mode should be Username


Test Complete/Execute should be installed


License Server for TestComplete


Data Generator dlls should be registered


ReportViewer should be installed


XML editor (XML Notepad) for editing Store

Keywords library

Framework

Application

Configurations

Database

Output


Reduces absolute
dependency on
study.xml
correctness


Allows for
validating
changes across
study.xml builds


Bugs in study.xml
can be validated
by manual
intervention


Exemplified via PFT test keyword:



Reusable



One keyword works for all
PFT types e.g. PFT Pre,
PFT Post, Serial PFT


Global keyword works
-


across studies e.g.
070019, 001100, 00103


Across visits e.g. V2, V3,
V5


Flexible



Handles various
functional conditions
within the keyword


e.g. FEV1 condition for
Inclusion/ Exclusion
criteria

Configurable



Feed the parameter value
from keyword form or
store


e.g. Feed FEV1 value from
PFT keyword form or
generate using Store/DG
dynamically

Stores configuration keys in separate xml

Readable format

Hard/Soft rule ranges

Criteria, Formula

Messages

Supports Versioning

Independent Component

Data Types


Integer, Text, Float, RegEx,
CodeList

Positive & Negative Data

Cater to Hard & Soft Rules


-
1

-
1
-


0, 17

0
-

17


18, 75

18
-

75


76, 90

76


90


91

91
-

Soft Rule

Hard Rule

Data Generated

for both rule types

Smoke/

Regression
Testing

Load/

Integration
Testing

Types of
testing
covered

System/

Study
Testing

Expert 3

Keyword1

Positive

B&C

Ambient Condition





Backup





Change Date Time



Change Site Information





Create Store



Create Subject





Device Check



Dosing





End Visit



Inclusion





Launch MSCCT32



Login





Keyword

Positive

B&C

Restore





Serial PFT





ShutDown



Validate Icon



Validate Study





Visit Calender



Waiting Room



Patient Details





User Management





Randomization





Reschedule Visit



Keyword

Positive

B&C

New Message



Study Help



Data Transfer



Search Patient





Start Visit





New DCR



System Time



System Access



LogOff





PFT





Closed system

Calibration

Amend PFT

Linearity check

Installation of new study

Calibration check

Battery mode

Calibration log

Print Manager

Linearity check log

System Information

Calibration check log

Update

Proficiency mode login

Remote login

Fingerprint authentication login

Data transfer configuration

Temporary password login

Crowbar

Visit summary

System Log and Audit Trail

Print functionality


Install automation using Installer


Create/Use Automation Project


Create Keyword Tests


Execute Test Scenarios


View/Evaluate Reports


Run keywords in the order:

Create Patient,
Backup, Patient details,
Restore, Search Patient

Scenario 1

Executes Backup test script with
Test ID: BAK_02_001103


Validate Study (+ve)


View reports

Scenario 2

Report Generation

(Data Input & Icon Reports)



Patient Details B&C

Scenario 3

Standard Functionality (Branch &
Condition)


Automatic Visit Reschedule using “Validate
Icon” and “Change Date and Time”
keywords

Scenario 4

Some specific items identified
during UAT



Validate Study B&C

Scenario 1

Complete Validation of study
end
-
to
-
end


Run keywords in the order:

Login, PFT, Dosing, Inclusion,
Randomization

Scenario 2

Workflow B&C keywords


Demonstration of store functionality and
its usage in different test scenarios

Scenario 3

Store implementation


Formula based inclusion/exclusion in PFT


Create multiple patients and data transfer

Scenario 4

Inclusion/exclusion and load
generation


Launch Masterscope, Backup,
Restore,
Ambient Condition, Change Site
Information, Data Transfer, Device Check

Scenario 1

Standard Functionalities Positive


Ambient Condition, Backup, Change Site
Information, Logoff, New DCR

Scenario 2

Standard Functionalitues B&C



Start Visit, End Visit, PFT, Dosing, Inclusion

Scenario 3

Workflow Functionalities Positive


Create Subject, Inclusion, Serial PFT, Start
Visit

Scenario 4

Workflow Functionalities B&C


Logoff, Search Patient, Shutdown, Visit
Calendar, Waiting Room, Patient Details,
User Management

Scenario 1

Standard Functionalities Positive


New Message, Restore, Search Patient,
Study Help, System Time, User
Management, Login

Scenario 2

Standard Functionalitues B&C


Login, Randomization, Reschedule Visit,
Serial PFT

Scenario 3

Workflow Functionalities Positive



System Access

Scenario 4

Validation of access rights for
Masterscope

user roles