1. Continuous Delivery
in an Ancient World
of Physical Devices
Manuel Pais
London Continuous Delivery
20th
April 2016

2. Agenda
An Ancient World
Forget Physical Laws
Layered World
Parallel Worlds
Beyond Test Automation

3. An Ancient World

5. <insert latest Docker
orchestration diagram>

6. Not for everyone

8. Context

12. Do desktop applications still make
sense?

13. IF you have to integrate with
low-level SDKs

14. IF client app requires low
latency

15. IF your stress tests look like
this…

26. Forget Physical Laws

27. Test automation
with
physical devices ?!

29. Not a great fit for
Continuous Delivery…

30. byte[] start_scan()
char[] capture()
char[] scan_finger()

31. Plain Old Interfaces

33. Decoupled Development

34. Decoupled Development
x. Device Integration

35. Decoupled Development
x. Device Integration
y. Application
Biometric Logic

36. byte[] start_scan();

37. Test Data Management

38. Given a complete Visa application
When I capture 4 valid fingerprints
Then application is sent for approval

39. Given a traveler leaving the country
When 1 finger is missing
Then border supervisor is called

40. Forget Physical Laws
Problem
Automate testing of applications using
physical devices
Solution
• Common interface for similar devices
• Virtual device implementation for that
interface
• Test data management

41. Layered World

42. Reusable core modules

43. Reusable core modules
but
Many customizations

44. Reusable core modules
but
Many customizations
and
Specific customer
requirements ?

46. Plain Old Layers

48. Low level UI
automation
across all
apps

49. Low level UI
automation
across all
apps

50. Low level UI
automation
across all
apps
Module
“object”
automation

51. Low level UI
automation
across all
apps
Module
“object”
automation

52. Low level UI
automation
across all
apps
Module
“object”
automation
Application
logic
automation

53. Low level UI
automation
across all
apps
Module
“object”
automation
Application
logic
automation

54. Low level UI
automation
across all
apps
Module
“object”
automation
Application
logic
automation

55. Layered World
Problem
Automate testing of reusable client modules
with project customizations and specific
requirements
Solution
Layered test code: pure UI + module logic +
application logic

56. Parallel Worlds

57. Multiple
public-facing interfaces

58. GUI vs API

59. OR

60. Novice Users
vs
Power Users

61. Plain old
Dependency Injection

65. FingerprintsSho
rtcuts
IFingerprints
Given a complete Visa application
When I capture 4 valid fingerprints
Then application is sent for approval
Fingerprints
UI
Fingerprint.IFingerprints
=
Fingerprint.FingerprintsUI

66. FingerprintsSho
rtcuts
IFingerprints
Fingerprints
UI
Fingerprint.IFingerprints
=
Fingerprint.FingerprintsShortcuts
Given a complete Visa application
When I capture 4 valid fingerprints
Then application is sent for approval

67. Parallel Worlds
Problem
Automate testing of multiple
interfaces/executions for same scenario
Solution
A single test interface for the exposed
functionality
Two or more implementations of that interface
(Basic) dependency injection mechanism

68. Beyond Test Automation

71. CI
SERVER
Vagrant-cloudstack
Commit
to Repo
Vagrant-
VirtualBox
Build
Success
Developer

72. Test Platform
VM
Destroy
VM
Create
New
VM
Destroy
VM
Test
run
Create
New
VM
Integration
Unit
tests
Integrati
on tests
Smoke Test
Subset
of
accepta
nce
tests
Acceptance
Tests
All other
accepta
nce
tests
Manual
Tests
Manual
scenario
s
Explorat
ory tests
From
CI
SERVER
Test
run
Test Workstation or
Static VM
Test
run
Test
run
Accept
or Reject
72

73. Integration
Unit
tests
Int &
Smoke Test
Integration
tests
Subset of
acceptance
tests
Acceptance
Tests
All other
accepta
nce
tests
Manual
Tests
Manual
scenarios
Exploratory
tests
CI
SERVER
Test
run
Vagrant-cloudstack
Create
New
VM
Test
run
Test
run
Destroy
VM
Vagrant-
cloudstack
Create
New
VM
Destroy
VM
Test
run
Accept
or Reject
73
To

74. Thank you!

75. Q & A