1
\documentclass[a4paper, 12pt]{article}
4
pdfauthor={Antti Kaijanm\"{a}ki},
13
\title{ZinC\\Service Description Language\\---\\Service and Client Testing}
15
Antti Kaijanm\"{a}ki\\
16
\texttt{antti.kaijanmaki@canonical.com}
21
\pagenumbering{gobble}
32
\pagenumbering{arabic}
34
fuzzing, range checking, mocking
36
\section{testability story}
37
play around with the transport, easy mocking, autogeneratored mocking tools
38
remote services, etc.. etc..
42
\fbox{\includegraphics[width=0.8\textwidth]{images/testing.png}}
43
\caption{Awesome Image}
44
\label{fig:awesome_image}
47
instead of testing individual services on dbus-level and separately on each client library implementation the testing efforts only need to be concentrated around the generators. for service backends we get a nice higher level testing surface instead of painfully doing testing on dbus level.
49
when the generators are carefully tested, we can trust them to work properly in general and then split the testing focus from "full stack" to backend and clients. see the picture.