SLIDE 1
eMCee web API tester Norbert Hartl 2denker What we do... ...at - - PowerPoint PPT Presentation
eMCee web API tester Norbert Hartl 2denker What we do... ...at - - PowerPoint PPT Presentation
eMCee web API tester Norbert Hartl 2denker What we do... ...at 2denker mobile applications backend services for mobile applications backend services for b2b all services are REST or SOAP Interface life cycle definition interface between
SLIDE 2
SLIDE 3
Interface life cycle
definition interface between server and client interface is implemented on the server interface is implemented on the client interface goes into production
SLIDE 4
Definition of interface
finding all parameters that are needed define a format to be used definition of workflows (sequences of action)
SLIDE 5
Server implementation
development starts late (timeframe same as client)
SLIDE 6
Server implementation
development starts late (timeframe same as client) goes online with reduced/dummy implementations
SLIDE 7
Server implementation
development starts late (timeframe same as client) goes online with reduced/dummy implementations partially spec conform
SLIDE 8
Server implementation
development starts late (timeframe same as client) goes online with reduced/dummy implementations partially spec conform changes frequently
SLIDE 9
Client implementation
has spec conform mocks develops all workflows against those mocks (even complex workflows) is ready at the same time or earlier than the server has sophisticated logging that eases debugging even if client is running on customer device
SLIDE 10
Client implementation
SLIDE 11
Client implementation
(honest version)
SLIDE 12
Client implementation
(honest version)
starts as soon as server is available (no mocking)
SLIDE 13
Client implementation
(honest version)
starts as soon as server is available (no mocking) gets errors through reduced/dummy implementations
SLIDE 14
Client implementation
(honest version)
starts as soon as server is available (no mocking) gets errors through reduced/dummy implementations determines new requirements for server interface
SLIDE 15
Client implementation
(honest version)
starts as soon as server is available (no mocking) gets errors through reduced/dummy implementations determines new requirements for server interface fails later through server interface changes
SLIDE 16
Client implementation
(honest version)
starts as soon as server is available (no mocking) gets errors through reduced/dummy implementations determines new requirements for server interface fails later through server interface changes logging of debug data is unsufficient to determine errornous side of interface
SLIDE 17
PRODUCTION
SLIDE 18
PRODUCTION
(again ... the honest version)
SLIDE 19
PRODUCTION
(again ... the honest version)
server interface changes are stopped shortly before going into production
SLIDE 20
PRODUCTION
(again ... the honest version)
server interface changes are stopped shortly before going into production client is tested through usage
SLIDE 21
PRODUCTION
(again ... the honest version)
server interface changes are stopped shortly before going into production client is tested through usage errors start popping up as soon as it is in production
SLIDE 22
PRODUCTION
(again ... the honest version)
server interface changes are stopped shortly before going into production client is tested through usage errors start popping up as soon as it is in production client is first suspect if something goes wrong
SLIDE 23
PRODUCTION
(again ... the honest version)
server interface changes are stopped shortly before going into production client is tested through usage errors start popping up as soon as it is in production client is first suspect if something goes wrong error discussion start always with „Maybe...“
SLIDE 24
eMCee tester
monitors currently defined interface periodically enables content checks (big help) sends notification if something changes snapshots requests to be able to analyze problem better (reproducability)
SLIDE 25
Demo
SLIDE 26
Questions?
SLIDE 27
Thank you!
visit us at http://2denker.de