Presenters: Gan Boon Leong • Larica Bawar • Miki Soo • Rizwanur Rashid Testing Recipe The iconnect360 Way
Aug 15, 2015
Presenters: Gan Boon Leong • Larica Bawar • Miki Soo • Rizwanur Rashid
Testing RecipeThe iconnect360 Way
SETs Team
Wan Yee LaricaRizwan
Chitrini
Daniel
Linda
Jin Rou
MikiGAN
AgendaSETs - EvolutionTest Process – The Ingredients!
Test PlanningTest DesignTest ExecutionTest Closure
Automation FrameworkQ & A
SETs Evolution2015
2014Defined processFormed test automation team
2013
2012No ProcessSharepoint for defects.
Test Process
Planning
Design
Execution
Closure
Planning
Planning
Identify Activities
Plan Resources & Scheduling
Identify Exit Criteria
Risk Analysis
Failure Probability Business Impact
$$$
Failure Probability
Usage Frequency
Taiga
Taiga
Monitor Issues
Monitor Daily Tasks Track User Stories
PrototypesConvert Tasks to Cards
Design
Design Activities
Requirements Analysis
Knowledge Sharing
Prepare Test Cases
Review/Revise Test Cases
Prepare Regression Test Plan
Prepare Test Data & Environment
Regression Test PlanMust Test
Could be tested
Test if time permits
Not possible to test everything!
Plan for Test Resource
Manage Test Build Manage Test Case
Manage Test Plan
TestLink
Test Data Preparation
Manual Approach Generatedata.com Migration Tool SETs Developed Tools
Test Execution
Test Execution FlowTest Case Execution
Report & Re-test Defects
Regression Testing(Manual &
Automated)
Smoke Testing
Test Types
Unit Testing
Who: Developers
Where:Local PC, QAAlpha
Why: To make sure individual components
are working
Feature Testing
Who: Testers
Where: QABeta
Why: To make sure new features are working as
intended
Regression Testing
Who:Testers
Where:QABeta,
Pre-production
Why: To make sure existing features are still
working
Smoke Testing
Who: Testers
Where: Cold Server, Production
Why: To make sure core functionalities are
working
Monitor Test Progress
Execute Test Cases
TestLink - Execution
Defect Life Cycle
NewIn
Progress Dev
In Progress SETs
ResolvedKIV
Test Closure
Test Closure Activities
Release Readiness
Prepare Release Readiness DocumentHold Release Readiness Meeting
Release Day
Smoke Testing (Production, Sales, Demo)Release (Go Live)
Post Release
Release RetrospectiveBugzilla Defect Metrics
Bugzilla Defect Metrics
Automation
Test Automation Process
Test Automation - FrameworkCustom Build Framework
Telerik Testing
FrameworkC#.NET Silverlight
Automation
Selenium Java HTML Automation
Custom Automation Framework - Reasons
More controlFreedom for end to end
process
Custom Logger
Less Maintenance
Effort
Less learning curve
Thinking About LayersTests
Custom Framework
Automation Framework (Selenium/Telerik Testing Framework)
Browser (Web App)
Each layer only interacts with the layer immediately
below it
Thinking About Layers (Cont.)Tests
Framework
Selenium
Browser (Web App)
Page Tests
Data Layer
Logger
Page Repositories
Entities
UI Object Repositories
Testlink Updater
Helper Factory
The framework itself is divided into layers of functionality
The Page Objects Model
Test
LoginPage::Code- login()- ResetPassword()ToggleRememberMe()
LoginPage::Browser
Selenium org.openqa.selenium.support.PageFactory
.NET – Custom design
Pages are good way to model the functionality of an application
Execution Flow
Loop for configured countries
Begin test
CSV data
IsRun =
true?
Test initialization
Test execution (Page > UI repo)
HTML logger::Write detail log with screenshot
Update Testlink (pass/fail result)
HTML logger::Write summary
log
End execution
Is last row?
Yes
Yes
No
No, proceed to next row
End to End Demo of
Silverlight Automation
Question & Answer
THANK YOU!