forked from hakimel/reveal.js
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathprophecy.html
More file actions
executable file
·449 lines (387 loc) · 15.3 KB
/
Copy pathprophecy.html
File metadata and controls
executable file
·449 lines (387 loc) · 15.3 KB
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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Testimony for developers</title>
<meta name="description" content="A short guide how to test your Laravel 4 application">
<meta name="author" content="Milan Popovic">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/black.css" id="theme">
<link rel="stylesheet" href="css/presentation/prophecy.css">
<!-- Code syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<h1>Test(imony)</h1>
<p>
<small>Presented by <a href="http://milanpopovic.me">Milan Popović</a> / <a href="http://twitter.com/komita1981">@komita1981</a></small>
</p>
</section>
<section>
<section>
<h2>Prophecy</h2>
<p>
Highly opinionated mocking framework for PHP 5.3+
</p>
<p>
Created by Konstantin Kudryashov and contributors
</p>
<p>
Initially it was created to fulfil phpspec2 needs
</p>
<p>
<pre><code data-trim contenteditable>
"require-dev": {
"phpspec/prophecy": "~1.0"
},
</code></pre>
</p>
</section>
<section>
<h2>Winds in the back</h2>
<p>
From version 4.5 PHPUnit is the out-of-the-box support for Prophecy
</p>
<p>
Developers will be encouraged to use Prophecy's API instead of the "classic" PHPUnit API
</p>
</section>
<section>
<p>
Every word has a logical meaning, even the name of the library itself (Prophecy)
</p>
<blockquote cite="https://github.com/phpspec/prophecy">
“Prophecy has been named that way because it concentrates on describing the future
behavior of objects with very limited knowledge about them. But as with any other prophecy,
those object prophecies can't create themselves - there should be a Prophet”
</blockquote>
<p>
<pre><code data-trim contenteditable>
$prophet = new Prophecy\Prophet;
</code></pre>
</p>
</section>
<section>
<blockquote cite="http://thephp.cc/news/2015/02/phpunit-4-5-and-prophecy">
“The prophet creates prophecies by prophesizing them. Test double objects are then
created by revealing their respective prophecy. You can think of a prophecy as the
configuration for a test double that is stored in an object separate from the object
(revelation) that acts as the test double.”
</blockquote>
<p class="fragment">
<span class="red_text">
Confused?
</span>
</p>
</section>
<section>
<p>
<pre><code data-trim contenteditable>
interface Reader
{
public function read();
}
class Processor
{
public function process(Reader $reader)
{
$reader->read('123');
// ...
}
}
</code></pre>
</p>
</section>
<section>
<h2>Dummy</h2>
<p>
<pre><code data-trim contenteditable>
class ProcessorTest extends PHPUnit_Framework_TestCase
{
public function testDataFromReaderCanBeProcessed()
{
$reader = $this->prophesize('Reader');
$processor = new Processor;
$processor->process($reader->reveal());
// ...
}
}
</code></pre>
</p>
</section>
<section>
<h2>Stub</h2>
<p>
<pre><code data-trim contenteditable>
class ProcessorTest extends PHPUnit_Framework_TestCase
{
public function testDataFromReaderCanBeProcessed()
{
$reader = $this->prophesize('Reader');
$reader->read('123')->willReturn('value');
$processor = new Processor;
$processor->process($reader->reveal());
// ...
}
}
</code></pre>
</p>
</section>
<section>
<h2>Mock</h2>
<p>
<pre><code data-trim contenteditable>
class ProcessorTest extends PHPUnit_Framework_TestCase
{
public function testDataFromReaderCanBeProcessed()
{
$reader = $this->prophesize('Reader');
$reader->read('123')->willReturn('value')->shouldBeCalled();
$processor = new Processor;
$processor->process($reader->reveal());
// ...
}
}
</code></pre>
</p>
</section>
<section>
<h2>Spies</h2>
<p>
<pre><code data-trim contenteditable>
$em = $prophet->prophesize('Doctrine\ORM\EntityManager');
$controller->createUser($em->reveal());
$em->flush()->shouldHaveBeenCalled();
</code></pre>
</p>
</section>
</section>
<section>
<section>
<h2>Prophecy vs Mockery</h2>
<p class="fragment">
Conceptual difference between Mockery and Prophecy
</p>
<p class="fragment">
Prophecy puts messaging before structure
</p>
<p class="fragment">
<span class="red_text">WHAT?</span>
</p>
<p class="fragment">
How objects communicate <span class="red_text">vs</span> When objects communicate
</p>
</section>
<section>
<h2>Packagist statistics</h2>
<p class="fragment">
Mockery - 1 524 884 total dowloads - 138 776 in last 30 days
</p>
<p class="fragment">
Mockery - 681 238 total dowloads - 153 463 in last 30 days
</p>
</section>
<section>
<p>
<pre><code data-trim contenteditable>
interface User
{
public function getRating();
public function setRating($rating);
}
class UserRatingCalculator
{
public function increaseUserRating(User $user, $add = 1)
{
$user->setRating($user->getRating() + $add);
}
}
</code></pre>
</section>
<section>
<p>
<pre><code data-trim contenteditable>
$user = Mockery::mock('User');
$user->shouldReceive('getRating')->andReturn(2);
$user->shouldReceive('setRating')->with(4)->once();
$calc = new UserRatingCalculator();
$calc->increaseUserRating($user->mock(), 2);
</code></pre>
</section>
<section>
<p>
<pre><code data-trim contenteditable>
$user = $prophet->prophesize('User');
$user->getRating()->willReturn(2);
$user->setRating(4)->shouldBeCalled();
$calc = new UserRatingCalculator();
$calc->increaseUserRating($user->reveal(), 2);
</code></pre>
</section>
<section>
<p>
<pre><code data-trim contenteditable>
class UserRatingCalculator
{
private $dispatcher;
public function __construct(EventDispatcher $dispatcher)
{
$this->dispatcher = $dispatcher;
}
public function increaseUserRating(User $user, $add = 1)
{
$this->dispatcher->userRatingIncreasing($user->getRating());
$user->setRating($user->getRating() + $add);
$this->dispatcher->userRatingIncreased($user->getRating());
}
}
</code></pre>
</section>
<section>
<p>
<pre><code data-trim contenteditable>
$user = Mockery::mock('User');
$user->shouldReceive('getRating')->andReturn(2, 2, 4);
$user->shouldReceive('setRating')->with(4)->once();
$disp = Mockery::mock('EventDispatcher');
$disp->shouldReceive('userRatingIncreasing')->with(2)->once();
$disp->shouldReceive('userRatingIncreased')->with(4)->once();
$calc = new UserRatingCalculator($disp->mock());
$calc->increaseUserRating($user->mock(), 2);
</code></pre>
</section>
<section>
<p>
Structure binding - it means your test is now bound to the way your code is structured
</p>
<p>
That there are 3 consequent getRating() calls in specific order
</p>
</section>
<section>
<p>
<pre><code data-trim contenteditable>
$user = $prophet->prophesize('User');
$user->getRating()->willReturn(2);
$user->setRating(Argument::type('integer'))->will(function($args) {
$this->getRating()->willReturn($args[0]);
});
$disp = $prophet->prophesize('EventDispatcher');
$disp->userRatingIncreasing(2)->shouldBeCalled();
$disp->userRatingIncreased(4)->shouldBeCalled();
$calc = new UserRatingCalculator($disp->reveal());
$calc->increaseUserRating($user->reveal(), 2);
</code></pre>
</p>
</section>
<section>
<p>
Message binding - it means that behaviour of the method does not change over time, but
rather is changed by the other method.
</p>
</section>
<section>
<p>
<pre><code data-trim contenteditable>
public function increaseUserRating(User $user, $add = 1)
{
$initialRating = $user->getRating();
$this->dispatcher->userRatingIncreasing($initialRating);
$user->setRating($initialRating + $add);
$resultingRating = $user->getRating();
$this->dispatcher->userRatingIncreased($resultingRating);
}
</code></pre>
</p>
</section>
<section>
<p class="fragment">What happened with test?</p>
<p class="fragment">Mockery tests failed - Prophecy test still pass</p>
<p class="fragment">Why</p>
<p class="fragment">Test was bound purely on communicational behaviour</p>
</section>
<section>
<h2>Review</h2>
<p>
conceptual difference is not in how you write tests, but when you fix them
</p>
<p>
Mockery sometimes could put you into the situation, where you would write tests that will
inevitably fail because of the private structural refactoring
</p>
<p>
Prophecy postulates that there is no failure in this case - because the actual behaviour stayed the same.
</p>
</section>
<section>
<h2>Can Mockery do the same?</h2>
<p class="fragment">Yes</p>
<p>
<pre><code data-trim contenteditable>
$user->shouldReceive("getRating")->andReturn(2)->byDefault();
$user->shouldReceive("setRating")->with(4)->andReturnUsing(function ($rating) use ($user) {
$user->shouldReceive("getRating")->andReturn($rating);
})->once();
</code></pre>
</p>
</section>
</section>
<section>
<ul>
<li><a href=""></a></li>
</ul>
</section>
<section>
<h1>THANK YOU</h1>
</section>
<section>
<h1>QUESTIONS?</h1>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
// Full list of configuration options available at:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
// Optional reveal.js plugins
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true, condition: function() { return !!document.querySelector( 'pre code' ); }, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true },
{ src: 'plugin/notes/notes.js', async: true }
]
});
</script>
</body>
</html>
<!--
@todo
Dodati jos neki primer za L4 - integration testing
-->