people behind the testing tools and frameworks · people behind the testing tools and frameworks...
TRANSCRIPT
Who we are… … Ranorex Mission
3
Focus: FunctionalUI Test Automation
API
4
User Base
2,000+ Customers
10,000+ Users
5
Ranorex Offices
Ranorex Mission
“Enable testers rising to meet their everyday challenge
of automated testing.”
Drivers for Test Automation
9
Drivers forTest Automation
Project Timeline
Analysis RequirementSpecification Design Imple‐
mentation
Testing
Delivery & Maintenance
Waterfall Approach
10
Drivers forTest Automation
» Software is already delivered
» Bad quality feedback from client
» „We haven‘t tested well enough…
» … because of time pressure.“
» „No time? –Automation Helps!“Driver: Management
11
Drivers forTest Automation
Implemen‐tation
Design
Specifi‐cation
Analysis
Shippable
Product
Testing
Agile
12
Drivers forTest Automation
Project Timeline
Implementation
Design
Specification
Analyse
ShippableProduct
Testing
Sprint 1
Implementation
Design
Specification
Analyse
ShippableProduct
Testing
Sprint 2
Implementation
Design
Specification
Analyse
ShippableProduct
Testing
Sprint n
Agile Approach
Driver: DevTeam
13
Roles in Test Automation
Test Manager
Test Director
Test Automation Specialist
Support Engineer
Software Architect
Test EngineerTest Analyst
Development Lead
Product Manager
Release Manager
Project ManagerTeam Lead Automation
14
RolesBetweenTwoExtremes?
Domain Tester
Technical Tester
User Base
Waterfall/V‐Model
Agile
„Water‐gile“
15
Technical Tester
» Test automation on code level
» Ranorex API power user
» „I‘m a frameworker –I don‘t want to depend on anything“
» Deeply integrated with SW development process
» Ranorex Studio often not in use
» Nearly no Ranorex support needed‐> Community‐driven
16
Domain Tester
» Domain Knowledge – Representing theUser
» Often separated from dev team and processes
» „In love“ with „Record“ button –Capture & Replay
» Afraid of code
17
RolesBetweenTwoExtremes
Domain Tester
Technical Tester
User Base
Waterfall/V‐Model
Agile
Level ofAutom
ationHIGH
MEDIUM
LOW
18
Real Life Customer Situation
Scope: Internal IT(SAP, HTML5, .NET)
Dev‐Approach: Multiple vendorsno in‐house dev‐team
Tools forQA: Ranorex, HP QCMicrosoft TFS
TA‐Approach: Ranorex Module Framework + Ranorex Recorder
TA‐Team: Internal + External
30% Technical Tester
70% Domain Tester
Scope: Tomography‐Software(.NET, MFC)
Dev‐Approach: in‐house, „Watergile“
Tools forQA: Ranorex, Microsoft TFS, in‐house solutions
TA‐Approach: Ranorex Code Module Framework, No‐Recorder, but Visual Studio
TA‐Team: Internal
90% Technical Tester
10% Domain Tester
19
ChallengesforTool Vendors
#1: Multiple UI technologies,multiple suppliers + shorter release cycles
#2: Test maintenance
#3: Finding the right people
20
Technologies
21
Multiple Technologies
Desktop Web
Mobile
BUILD?
BUY?
OUTSOURCE?
How to control software quality?
22
Multiple Technologies
» What‘s needed?
» Tools assisting with „Design forTestability“(for in‐house development)
» Automation frameworks delivered with solutions(outsourced development)
23
Test Maintenance
24
Test Maintenance
» What‘s needed?
» Smart ways to create out of the box UI maps at design time
25
Finding the Right People
26
Automation Expert –Skill‐Set
» Scripting/Development Background
» Ranorex Knowledge
» Tools & Processes
» Continuous Integration
» Test Management
» Communication Skills
27
Who uses Ranorex
Questions?
