training on automation solution for mscct32
DESCRIPTION
Training on Automation Solution for MSCCT32. Training Agenda. Data Generator Areas of Use List of Keywords Standard Positive Branch & Condition Exclusions Creating Scenarios Installer Creating Project Creating Keyword Tests Execution Reports Demo Scenarios & Hands On. - PowerPoint PPT PresentationTRANSCRIPT
Training on Automation Solution
for MSCCT32
1. Introduction - Objectives2. Introduction to Automation
1. Manual vs automation testing2. Main Advantages3. Limitations4. Introduction – Design Approach
3. Automation Tool – TestComplete1. Introduction2. Licenses3. TestComplete IDE4. TestExecute
4. MSCCT32 Automation1. System Requirements2. Dependencies3. Architecture4. Keywords Approach5. Store
Training Agenda
6. Data Generator7. Areas of Use
4. List of Keywords4. Standard5. Positive6. Branch & Condition
5. Exclusions6. Creating Scenarios
1. Installer2. Creating Project3. Creating Keyword Tests4. Execution5. Reports
7. Demo Scenarios & Hands On
Introduction - Objectives
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 TestsHigh 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
Introduction to Test Automation
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
Test Automation – Main advantages
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
Test Automation – Some limitations
Introduction – Design Approach
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 applicationsRecording 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
Automation Tool - TestComplete
Licenses
Node locked:- run on specific machines
- limited usage- no flexibility
Floating:- License server
- limited to concurrent usage
- complete flexibility
Automation Tool - TestComplete
TestComplete IDE
Automation Tool - TestComplete
Test Execute
Automation Tool - TestExecute
•MSCCT32 Laptop with 2 GB RAM
•LAN Connection for license
•Open System
•Validation Mode
•Dummy Mode
•Authentication Mode should be Username
MSCCT32 Automation –System Requirements
•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
MSCCT32 Automation - Dependencies
MSCCT32 Automation - Architecture
Keywords library
Framework
ApplicationConfigurations Database
Output
MSCCT32 Automation - Architecture 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
MSCCT32 Automation – Keywords Approach 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
MSCCT32 Automation - Store
Independent Component
Data Types – Integer, Text, Float, RegEx, CodeList
Positive & Negative Data
Cater to Hard & Soft Rules
MSCCT32 Automation – Data Generator
• -1
-1 -
• 0, 17
0 - 17
• 91
91 -
MSCCT32 Automation – Data Generator
Soft Rule
Hard Rule
Data Generatedfor both rule types
MSCCT32 Automation – Areas of Use
Smoke/Regression Testing
Load/Integration Testing
Types of testing covered
System/Study Testing
MSCCT32 Automation – Areas of Use
Expert 3
MSCCT32 Automation – Keywords List
Keyword1 Positive B&CAmbient Condition √ √Backup √ √Change Date Time √Change Site Information
√ √Create Store √Create Subject √ √Device Check √Dosing √ √End Visit √Inclusion √ √Launch MSCCT32 √Login √ √
MSCCT32 Automation – Keywords List
Keyword Positive B&CRestore √ √Serial PFT √ √ShutDown √Validate Icon
√Validate Study √ √Visit Calender √Waiting Room √Patient Details √ √User Management √ √Randomization √ √Reschedule Visit √
MSCCT32 Automation – Keywords List
Keyword Positive B&CNew Message √Study Help √Data Transfer √Search Patient
√ √Start Visit √ √New DCR √System Time √System Access √LogOff √ √PFT √ √
MSCCT32 Automation - Exclusions
Closed system CalibrationAmend PFT Linearity check Installation of new study Calibration check Battery mode Calibration logPrint Manager Linearity check logSystem Information Calibration check logUpdate Proficiency mode loginRemote login Fingerprint authentication loginData transfer configuration Temporary password loginCrowbar Visit summarySystem Log and Audit Trail Print functionality
•Install automation using Installer
•Create/Use Automation Project
•Create Keyword Tests
•Execute Test Scenarios
•View/Evaluate Reports
Creating Scenarios - Steps
Scenario 1Executes Backup test script with
Test ID: BAK_02_001103
• Run keywords in the order: Create Patient,Backup, Patient details, Restore, Search Patient
Scenario 2Report Generation
(Data Input & Icon Reports)
• Validate Study (+ve)• View reports
Scenario 3Standard Functionality (Branch
& Condition)• Patient Details B&C
Scenario 4Some specific items identified
during UAT
• Automatic Visit Reschedule using “Validate Icon” and “Change Date and Time” keywords
Demo: Test Scenarios Day-1
Scenario 1Complete Validation of study
end-to-end• Validate Study B&C
Scenario 2Workflow B&C keywords
• Run keywords in the order: Login, PFT, Dosing, Inclusion, Randomization
Scenario 3Store implementation
• Demonstration of store functionality and its usage in different test scenarios
Scenario 4Inclusion/exclusion and load
generation
• Formula based inclusion/exclusion in PFT
• Create multiple patients and data transfer
Demo: Test Scenarios Day-2
Scenario 1Standard Functionalities Positive
• Launch Masterscope, Backup, Restore, Ambient Condition, Change Site Information, Data Transfer, Device Check
Scenario 2Standard Functionalitues B&C
• Ambient Condition, Backup, Change Site Information, Logoff, New DCR
Scenario 3Workflow Functionalities Positive
• Start Visit, End Visit, PFT, Dosing, Inclusion
Scenario 4Workflow Functionalities B&C
• Create Subject, Inclusion, Serial PFT, Start Visit
Demo: Test Scenarios Day-3
Scenario 1Standard Functionalities Positive
• Logoff, Search Patient, Shutdown, Visit Calendar, Waiting Room, Patient Details, User Management
Scenario 2Standard Functionalitues B&C
• New Message, Restore, Search Patient, Study Help, System Time, User Management, Login
Scenario 3Workflow Functionalities Positive
• Login, Randomization, Reschedule Visit, Serial PFT
Scenario 4Validation of access rights for
Masterscope user roles• System Access
Demo: Test Scenarios Day-4