-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
1057 lines (923 loc) · 46.8 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html prefix="og: http://ogp.me/ns#">
<head>
<title>Once Upon A Time In Software Testing - William Durand</title>
<link rel="stylesheet" href="css/reveal-no-icons.min.css">
<link rel="stylesheet" href="reveal.js/css/theme/serif.css" id="theme">
<link rel="stylesheet" href="reveal.js/lib/css/zenburn.css">
<link rel="stylesheet" href="font-awesome/css/font-awesome.min.css">
<link rel="stylesheet" href="css/custom.css">
<script>
document.write('<link rel="stylesheet" href="reveal.js/css/print/' +
(window.location.search.match(/print-pdf/gi) ? 'pdf' : 'paper') +
'.css" type="text/css" media="print">'
);
</script>
<meta property="og:title" content="Once Upon A Time In Software Testing - William Durand">
<meta property="og:description" content="Ever wondered what my daily job was?">
<meta property="og:image" content="http://williamdurand.fr/ouatist-slides/images/slide_0.png">
</head>
<body>
<div class="reveal">
<div class="slides">
<section>
<h1 class="title">Once Upon A Time In Software Testing</h1>
<em>William Durand - December 18, 2013</em>
</section>
<section>
<section data-markdown>
<script type="text/template">
## About Me
<br>
* PhD student at Michelin / LIMOS
* Graduated from IUT and ISIMA
* I <i class="icon-heart"></i> Open Source
<img src="images/clermontech.png" class="clermontech-badge" />
</script>
</section>
<section data-markdown>
<script type="text/template">
## PhD Topic
<br>
Automated **Test** Generation for applications and production machines in a
**Model-based Testing** approach.
</script>
</section>
</section>
<section data-markdown>
<script type="text/template">
## Agenda
<br>
* Introduction
* Verification Quickly
* Testing 101
* Model-based Testing
* Current Research
* Conclusion
</script>
</section>
<section>
<section data-markdown>
<script type="text/template">
## So... Software Testing
<p class="fragment">
<br>
**Software testing** is the process of **analyzing a software**
<br>item **to detect the differences between existing and
<br>required conditions** (that is, bugs) and to evaluate the
<br>features of the software item.
</p>
<p class="fragment">
<br>
It is a **verification** and **validation** process.
</p>
<p class="fragment">
<br>
**Validation** → "Are we building the right software?"
<br>
<br>
**Verification** → "Are we building the software right?"
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Why?
<br>
<ul>
<li>To find **faults** (G. Myers, The Art of Software Testing)</li>
<br>
<li>To provide **confidence** of reliability, correctness,<br>and absence of particular faults</li>
</ul>
<br>
<br>
<i class="icon-warning-sign"></i> This does **not** mean that the software is completely
free of defects. Rather, it must be good enough for its intended use.
</script>
</section>
<section data-markdown>
<script type="text/template">
## How?
</script>
</section>
<section data-markdown>
<script type="text/template">
## Industry
**Unit** Testing, **Integration** Testing, **Functional** Testing, System Testing,
Stress Testing, Performance Testing, Usability Testing, Acceptance Testing,
Regression Testing, Beta Testing, <Whatever You Want> Testing
<br><br>
<p class="fragment left">
<i class="icon-thumbs-up"></i> People now understand the need for testing things
</p>
<p class="fragment left">
<i class="icon-thumbs-down"></i> They mostly do testing by hand
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Academia
<p class="fragment">
</p>
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## Verification Quickly
</script>
</section>
<section data-markdown>
<script type="text/template">
## Definition
<br>
**Formal Verification** is the act of proving or disproving the
correctness of intended algorithms underlying a system<br>with
respect to a certain **formal specification or property**,<br>using
formal methods of **mathematics**.
<br>
<h4 class="left">Advantages</h4>
* **Powerful method** for finding software errors
* Mathematical **proof** of absence of errors in models relative to specifications
</script>
</section>
<section data-markdown>
<script type="text/template">
## Techniques
<br>
* Model Checking
* Runtime Verification
* Theorem Proving
* Static Analysis
* Simulation
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## Testing 101
</script>
</section>
<section data-markdown>
<script type="text/template">
## Definition
<br>
**Software Testing** is the process of executing a program or system
with the intent of finding errors.
However, "Testing shows the presence, not the absence of bugs" (Dijkstra).
<br>
<p>
<i class="icon-info-sign"></i> It is the **validation** part!
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## The Big Picture
<br>
<img src="images/test.png" />
</script>
</section>
<section data-markdown>
<script type="text/template">
## Test Suite
<br>
A **Test Suite** (TS) is a set of **Test Cases**.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Test Case
<br>
A **Test Case** (TC) consists of:
* Test Data (TD)
* Expected behavior
* Expected output
</script>
</section>
<section data-markdown>
<script type="text/template">
## Test Data
<br>
Inputs which have been devised to test the system.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Tester
<br>
A **tester** is a mechanism used for determining<br> whether a test has **passed** or **failed**.
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Test Execution
<br>
<img src="images/test_annotated.png" />
</script>
</section>
<section data-markdown>
<script type="text/template">
## Different Approaches
</script>
</section>
<section data-markdown>
<script type="text/template">
## White-Box Testing
<br>
**White-box testing** is a method that tests the **internal<br>structure** of
a **S**ystem **U**nder **T**est (SUT).
<br>
**Implementation**: a realistic, executable piece of software<br>or hardware that
should provide desired behaviors.
<br>
<i class="icon-info-sign"></i> It is usually done at the **unit** level.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Black-box Testing
<br>
**Black-box testing** is a method that tests the functionalities<br>of a
SUT **without knowing its internal structure**.
<br>
**Specification**: a description of the desired behaviors that define
only what the system should do, not how it is done.
<br>
<i class="icon-info-sign"></i> Also known as **Functional Testing**.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Grey-box Testing
<br>
The combination of **White-box** testing and **Black-box** testing.
<br>
You have access to the relevant internal parts of your SUT.
</script>
</section>
<section data-markdown>
<script type="text/template">
## But...
<br>
Testing cannot guarantee the absence of faults.
<i class="icon-arrow-down"></i>
How to select subset of Test Cases from all possible<br>Test Cases
with a high chance of detecting most faults?
</script>
</section>
<section data-markdown>
<script type="text/template">
## Test Selection (Strategies)
<p class="left">
<br>
**Black-box Testing**: Combinatorial Testing (Pairwise),
Equivalence Partitioning, Boundary Value Analysis,
<br>Function Coverage
<br>
<br>
**White-box Testing**: Fuzz Testing (Random), Statistical
Testing, Statement Testing, Path Testing, Branch Testing,
Condition Testing, Multiple Condition (MC) Testing, Loop
Testing, Mutation Testing
</p>
<br>
<small>
<a href="http://people.cs.aau.dk/~bnielsen/TOV07/lektioner/whitebox-07.pdf">http://people.cs.aau.dk/~bnielsen/TOV07/lektioner/whitebox-07.pdf</a>
</small>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Automatic Test Generation
<p class="fragment">
<br>
**White-box Testing** → Automatic Testing
<br>
<br>
**Black-box Testing** → Model-based Testing
</p>
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## Model-based Testing
</script>
</section>
<section data-markdown>
<script type="text/template">
## Definition
<br>
**Model-based Testing** (MbT) is **application of Model-based design** for designing and
optionally also executing artifacts<br>**to perform software testing**.
<br>
**Models** can be used to represent the **desired behavior<br>of an SUT**, or to represent
**testing strategies** and a **test environement**.
<br>
<small>
<a href="http://en.wikipedia.org/wiki/Model-based_testing">http://en.wikipedia.org/wiki/Model-based_testing</a>
</small>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Why?
<br>
* The need for automation
* Formal methods
</script>
</section>
<section data-markdown>
<script type="text/template">
## Goals
<br>
* To bring the benefits of automation to new parts of the test cycle
(test cases creation for instance)
* To provide testers more effective tools
* To reduce cost and cycle time
</script>
</section>
<section data-markdown>
<script type="text/template">
## The Big Picture
</script>
</section>
<section data-markdown>
<script type="text/template">
## Three Stages
<br>
1. Formally modelling the requirements (specification);
2. Generating test cases from the model;
3. Running these test cases against an actual SUT and evaluating the results.
<br>
<i class="icon-info-sign"></i> Combining 2. and 3. leads to **On-The-Fly Testing**.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Models
<br>
A **Model** is a description of a system that helps you understand and predict its behavior.
<br>
<br>
It does **not need to completely describe it** to be effective.
<br>
<br>
<p class="left">
**Behavior/Control oriented**: Finite Automata (FSM, LTS), Petri Nets,
Synchronous Languages (Lustre, Scade)
<br>
<br>
**Data oriented** (pre/post): JML, Spec#, OCL, B-Method, Praspel
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Observations
<br>
Executing a test case on a system yields a set of **observations**.
<br>
Every observation represents a part of the<br>**implementation model** of the system.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Implementation Model
<br>
The set of all observations made with all possible test cases represents the complete implementation
model of the system.
<br>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Testing Hypothesis
<br>
For every system there is a corresponding observational equivalent implementation model:
<br>
$$ \forall\ iut \in IMPS,\ \exists\ I_{iut} \in MODS $$
<br>
<ul class="left force-inline">
<li>$$ iut \in IMPS $$ is a concrete **I**mplementation **U**nder **T**est (IUT)</li>
<li>$$ IMPS $$ is the universe of implementations</li>
<li>$$ I_{iut} $$ is a model of $$ iut $$</li>
<li>$$ MODS $$ is the universe of the models of all IUT</li>
</ul>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Implementation Relation
<br>
<p class="force-inline">
To define conformance between an implementation under test $$ imp $$ and a specification $$ Spec $$,
we use the notion of an **implementation relation**:
</p>
<br>
$$ imp \subseteq MODS \times SPECS $$
<br>
<p class="force-inline">
with $$ SPECS $$ the set of specifications.
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Conformance
<p class="force-inline">
An implementation $$ iut $$ **conforms to** a specification $$ Spec $$ if the existing
model $$ I_{iut} $$ of $$ iut $$ is **imp-related to** $$ Spec $$.
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Conformance Testing
<p class="force-inline">
<br>
**Conformance Testing** assesses conformance to an **unknown** implementation under
test ($$ iut $$) to its specification ($$ Spec $$)<br>by means of **test experiments**.
<br>
<br>
Experiments consist of **stimulating** $$ iut $$ in certain ways and **observing** its
reactions. This process is called **test execution**.
</p>
</script>
</section>
<section>
<h2>Test Execution</h2>
<p class="force-inline">
<br>
Successful execution of a test case $$ TC $$:
</p>
<p>
$$ I_{iut}\ {\bf passes}\ TC $$
</p>
<p class="force-inline">
<br>
It is easily extended to a test suite $$ TS $$:
</p>
<p>
$$ I_{iut}\ {\bf passes}\ TS \Leftrightarrow \forall\ TC \in TS : I_{iut}\ {\bf passes}\ TC $$
</p>
<p class="force-inline">
<br>
<i class="icon-info-sign"></i> $$ I_{iut}\ {\bf fails}\ TC \Leftrightarrow I_{iut}\ \cancel{\bf passes} TC $$
</p>
</section>
<section data-markdown>
<script type="text/template">
## Test Suite Properties
<br>
<p class="left">
**Soundness**
<br>$$ \forall\ iut \in IMPS \dot\ [ (iut\ conforms\ to\ Spec) \Rightarrow (iut\ passes\ TS) ] $$
</p>
<p class="left">
**Exhaustiveness**
<br>$$ \forall\ iut \in IMPS \dot\ [ (iut\ passes\ TS) \Rightarrow (iut\ conforms\ to\ Spec) ] $$
</p>
<p class="left">
**Completeness**
<br>$$ \forall\ iut \in IMPS \dot\ [ (iut\ conforms\ to\ Spec) \Leftrightarrow (iut\ passes\ TS) ] $$
</p>
<br>
<p class="force-inline"><i class="icon-info-sign"></i> $$ TS \subseteq TESTS $$ is a test suite.</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Test Architecture
<p class="force-inline">
<br>
A **test architecture** is an abstract description of the **environment** in which an
implementation under test ($$ iut $$) is embedded, and where it communicates with a
**tester**.
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Test Generation
<br>
* Based on Finite State Machines
* Based on Symbolic Transition Systems
* Based on Labelled Transition Systems
</script>
</section>
<section data-markdown>
<script type="text/template">
## Labelled Transition System
<br>
A **L**abelled **T**ransition **S**ystem (LTS) describes the transitions from one state
to the other, caused by **action execution**.
<br>
$$ L = (S, Act, \rightarrow) $$
<br>
<ul class="left">
<li><code>S</code> is a set of states</li>
<li><code>Act</code> is a set of actions</li>
<li>$$ \rightarrow \subseteq S \times ( Act \cup \lbrace \tau \rbrace) \times S $$</li>
<li><code>τ</code> is a **silent**, unobservable action</li>
</ul>
</script>
</section>
<section>
<h2>Example</h2>
<br>
<p class="float-left">
<img src="images/lts.png" />
</p>
<p class="float-right">
<br>
$$ L = (S, Act, \rightarrow) $$
<br>
with
<br>
$$ S = \lbrace s_{1}, s_{2}, s_{3}, s_{4} \rbrace $$
<br>
and
<br>
$$ Act = \lbrace COFFEE, TEA, BUTTON \rbrace $$
</p>
</section>
<section data-markdown>
<script type="text/template">
## Traces
<br>
Traces describe the **observable behavior** of LTS.
<br>
$$ traces(s) = \lbrace \sigma | s \stackrel{\sigma}{\Longrightarrow} \rbrace $$
<br>
with
$$ s \in S $$
<p class="force-inline">
<br>
<i class="icon-info-sign"></i> The $$ \Longrightarrow $$ relation is used to abstract from $$ \tau $$ transitions.
</p>
</script>
</section>
<section>
<h2>Example</h2>
<p>
<br>
$$
\begin{align}
traces(s_{3}) =
& \lbrace \\
& BUTTON, \\
& BUTTON \cdot TEA \cdot BUTTON, \\
& \dots \rbrace = traces(s_{1}) = traces(s_{4}) \\
\\
traces(s_{2}) =
& \lbrace \\
& TEA, \\
& COFFEE, \\
& TEA \cdot BUTTON \cdot TEA, \\
& \dots \rbrace
\end{align}
$$
</p>
</section>
<section>
<h2>Input/Output LTS</h2>
<p class="force-inline">
<br>
By partitioning the actions labels ($$ Act $$) into <strong>inputs</strong> ($$ Act_{I} $$)
<br>and <strong>outputs</strong> ($$ Act_{U} $$), we can obtain an IOLTS:
</p>
<p>
<br>
$$ Act = Act_{I} \cup Act_{U} $$
</p>
<p class="force-inline">
<br>
The names of <strong>input actions</strong> end on "$$ ? $$", and
<br>those of <strong>output actions</strong> with "$$ ! $$".
</p>
<br>
<p>
<i class="icon-info-sign"></i> We introduce a special action δ to denote <strong>quiescence</strong>.
</p>
</section>
<section>
<h2>Example</h2>
<br>
<p class="float-left">
<img src="images/iolts.png" />
</p>
<p class="float-right">
<br>
<br>
<br>
$$
\begin{align}
Act_{I} = & \lbrace BUTTON?, COFFEE?, TEA? \rbrace \\
Act_{U} = & \lbrace COFFEE!, TEA! \rbrace
\end{align}
$$
</p>
</section>
<section data-markdown>
<script type="text/template">
## Conformance Relation
<br>
Relating two LTS can be done in a variety of manners:
<br>
<br>
* **Equivalence Relations**: Isomorphism, Bisimulation, Trace Equivalence, Testing Equivalence,
Refusal Equivalence;
* **Preorder Relations**: Observation Preorder, Trace Preorder, Testing Preorder, Refusal Preorder;
* **Input-Output Relations**: Input-Output Testing, Input-Output Refusal, **ioconf**, **ioco**.
<br>
<i class="icon-warning-sign"></i> Not all relations are suited for testing purposes.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Trace Preorder
</script>
</section>
<section data-markdown>
<script type="text/template">
## ioco
<br>
Common implementation relation for IOLTS:
$$ i\ ioco\ s = \forall\ \sigma \in straces(s) : out(i\ after\ \sigma) \subseteq out (s\ after\ \sigma) $$
<br>
<p class="left">
$$ i\ ioco\ s $$
<ul class="force-inline">
<li>
if $$ i $$ produces output $$ x $$ after trace $$ \sigma $$,
then $$ s $$ can produce $$ x $$ after trace $$ \sigma $$
</li>
<li>
if $$ i $$ cannot produce any output after trace $$ \sigma $$,
then $$ s $$ cannot produce any output after trace $$ \sigma $$ (quiescence)
</li>
</ul>
</p>
<p>
<br>
<i class="icon-info-sign"></i> A few tools: TorX, TGV, Autolink, TestComposer.
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Test Case
<div class="left float-left">
<br>
<br>
A **Test Case** is an IOLTS:
<ul>
<br>
<li>modeling the observation of **quiescence**</li>
<li>being **tree-structured**</li>
<li>being **finite** and **deterministic**</li>
<li>having final states **pass** and **fail**</li>
</ul>
</div>
<p class="float-right">
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Parallel Execution
<br>
**Executing** a test case by putting it in parallel
with the implementation model, leading to a **verdict**.
</script>
</section>
<section data-markdown>
<script type="text/template">
## So... What?
<br>
<p class="fragment">
Creating the **specification model** is complicated.
</p>
<br>
<p class="fragment">
But then, it is possible to do cool stuff!
</p>
<br>
<p class="fragment">
What about **automatically generating** it?
</p>
</script>
</section>
<section data-markdown>
<script type="text/template">
## Automated Generation Of Specification Models
<br>
* By leveraging the API documentation
* By **instrumenting** the code (tracing)
* By leveraging the logs
* By **monitoring** the system
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## Current Research
</script>
</section>
<section data-markdown>
<script type="text/template">
## Challenge
<br>
Based on a software, running in a<br>production environment, would it possible to:
<br>
<br>
1. extract a **knowledge base**
2. that can be formalized by a **model**
3. that can be used to **generate tests** and/or **specifications**?
</script>
</section>
<section>
<h2>Context (1/2)</h2>
<br>
<p>
Michelin relies on a method close to the <strong>C</strong>omputer <strong>I</strong>ntegrated <strong>M</strong>anufacturing
(CIM) approach to control its production:
</p>
<div class="float-left" style="width: 65%">
<ul style="margin-top: 5%">
<li>L4: Business Software</li>
<li>L3: Virtual level as it is not that used (Factory Management)</li>
<li><strong>L2: Supervision / Workshop Management</strong></li>
<li>L1: Automata</li>
</ul>
</div>
<div class="float-right" style="width: 60%">
<img src="images/levels.png" />
</div>
<p>These levels can exchange data among them.</p>
</section>
<section data-markdown>
<script type="text/template">
## Context (2/2)
<br>
Focus on **Level 2** applications but, then again,
<br>there are a lot of differences between them, such as:
* Programming Language
* Framework
* Design
* Version
</script>
</section>
<section data-markdown>
<script type="text/template">
## Hypotheses
<br>
1. Applications deployed in production behave as expected
2. Don't consider (existing) specifications
</script>
</section>
<section data-markdown>
<script type="text/template">
## The Big Picture
</script>
</section>
<section data-markdown>
<script type="text/template">
## Work In Progress
</script>
</section>
<section data-markdown>
<script type="text/template">
## What Can We Do?
<br>
* Test Data can be **inferred** from recorded data
* "Easy" record & replay
* Generation of a **degraded model**
* Generation of documentation and/or specification
* Generation of tests (code)
</script>
</section>
<section data-markdown>
<script type="text/template">
## **Auto**matic **Funk**tional Testing Tool
<br>
A **monitor** records incoming/outgoing data (traces).
<br>
An **Expert System** is used to generate models.
<br>
The tool communicates with an **explorer** to "feed" itself.
<br>
Based on the model, it is possible to generate test cases.
</script>
</section>
<section data-markdown>
<script type="text/template">
## **Auto**matic **Funk**tional Testing Tool
<br>
Written in Java, PHP, Node.JS, and JavaScript.
<br>
Distributed system thanks to RabbitMQ.
<br>
Service Oriented Architecture FTW!
<br>
<i class="icon-warning-sign"></i> This tool has been built for web applications.
<br>Michelin will get its own internal tool.
</script>
</section>
<section data-markdown>
<script type="text/template">
## Perspectives
<br>
* Formalizing the **different generated models** (WIP)
* Proving the correctness of each model (WIP)
* Test Data generation (WIP)
* Adding more rules to the Expert System
* Generating Test Cases
* Improving generated code
<br>
<i class="icon-hand-right"></i> Adapting this work for Michelin needs.
</script>
</section>
</section>
<section>
<section data-markdown>
<script type="text/template">
## Conclusion
<br>
Model-based Testing is the **next upcoming change**<br>in the industry, and it has already begun!
<br>
Michelin gives me a great opportunity to validate my experiments, and to develop a realistic
tool coming from academia for the industry.
</script>
</section>
</section>
<section data-markdown>