/
index.html
executable file
·985 lines (795 loc) · 31.4 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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Industrial JavaScript - Swiip</title>
<meta name="description" content="A framework for easily creating beautiful presentations using HTML">
<meta name="author" content="Hakim El Hattab">
<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">
<link rel="stylesheet" href="css/reveal.min.css">
<link rel="stylesheet" href="css/theme/blood.css" id="theme">
<!-- For syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- If the query includes 'print-pdf', use the PDF print sheet -->
<script>
document.write( '<link rel="stylesheet" href="css/print/' + ( window.location.search.match( /print-pdf/gi ) ? 'pdf' : 'paper' ) + '.css" type="text/css" media="print">' );
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<div class="slides">
<section>
<h1>Industrial JavaScript</h1>
<aside class="notes">
- Bringing JavaScript development to enterprise
- Especially in big enterprises
- Massive workflows
</aside>
<aside class="hide">
Hello everyone. I'm going to talk to you today about bringing JavaScript development in enterprise. Especially in big enterprises which have massive industrial workflows.
</aside>
</section>
<section>
<h2>
<a href="https://twitter.com/Swiip" style="color: white;">
<img src="img/Twitter_logo_blue.png" style="height: 80px; vertical-align: middle; border: none; box-shadow: none; background-color: transparent;" />
<img src="img/swiip.jpg" style="vertical-align: middle;" />
@Swiip
</a>
</h2>
<img src="img/logo-zenika.jpg" height="200" />
<img src="img/lyonjs.png" height="200" style="background-color: white;" />
<aside class="notes">
- Litle word about myself
- Matthieu Lux from Lyon
- Zenika, an IT service company specialized in Java
- I also run the Lyon JavaScript meetup
</aside>
<aside class="hide">
First off all, a little word about myself. I don't usually talk to much about myself but today I wanted to start with a little personal story. So, I'm Matthieu Lux from Lyon. I work at Zenika which an IT service company specialized in Java and I also run the Lyon JavaScript meetup.
</aside>
</section>
<section>
<h3>I'm involved in both Java and JavaScript communities</h3>
<div class="js"><div>JAVA</div></div>
<img src="img/JavaScriptLogo.png" height="300"/>
<aside class="notes">
- Mix up the two languages
- Involved in both communities
- Java developer in a Web conference could be hard
- Web community has a bad image of Java developers
</aside>
<aside class="hide">
As you can see, I mix up the two langages and the two communities. I'm involved in both Java and JavaScript communities. To be honest, being a Java developer in a Web conference could be hard. The Web community as such a bad image for Java developers.
</aside>
</section>
<section>
<h2>Java ?</h2>
<img src="img/coming_out.jpg" />
<h3>Yes, I "still" do Java<br> and I "still" enjoy it!</h3>
<aside class="notes">
- Still enjoy doing Java
- Not here to compare
- There is some good in Java and its ecosystem
</aside>
<aside class="hide">
But today, I choose to make my coming out. I'm a Java developer and I still enjoying doing Java. Or most of it. I'm not trying to compare here Java and JavaScript, I'm just saying that there is some good in Java and his ecosystem.
</aside>
</section>
<!--<section>
<h3>Worse, I do<br> Java "Enterprise Edition"</h3>
<img src="img/java-evil-edition.jpg" />
<h4>But with Spring... Sun and Oracle can go to Hell!</h4>
<aside class="notes">
I even do Java Enterprise Edition or Evil Edition for some people. The enterprise, industrial hard way to do Java. My point today, is to find some bridges betweens this two worlds to end up working together.
</aside>
</section>-->
<section>
<h3>I ended up working in<br>"big companies"</h3>
<aside class="notes">
- Leads to end up working in "big Java only companies"
</aside>
<aside class="hide">
Being a Java developer leads me to end up working in "big Java only companies".
</aside>
</section>
<section>
<h3>In these "big companies"...</h3>
<table>
<tr>
<td style="text-align: center;"><h4>Java<br>developer</h4></td>
<td style="text-align: center;"><h4>JavaScript<br>developer</h4></td>
</tr>
<tr>
<td><img src="img/business-man-resume.jpg" height="300" /></td>
<td><img src="img/hipster.jpg" height="300" /><td>
</tr>
</table>
<aside class="notes">
- Put the context
- Situation is different from a Web conference
- JavaScript developer is seen as a dangerous hipster
- Java developer is seen as a succesful businessman
</aside>
<aside class="hide">
To put the context of these companies, the situation is quite different than in a Web conference. It's the JavaScript developer who is seen as a dangerous hipster.
</aside>
</section>
<section>
<h3>Being a developer in one of these companies...</h3>
<aside class="notes">
- Being a developer is hard
- Powerfuls managers
- Respected senior architects
- Developers are only soldiers
</aside>
<aside class="hide">
In fact, just being a developer is hard. You know, you have the powerfuls managers and big respected senior architects, but developers are only laborer...
</aside>
</section>
<section>
<h3>Thinkpad forever</h3>
<img src="img/Encadre22709.jpg" />
<h4>1 GB Ram, Win XP (no kidding) Thinkpad</h4>
<aside class="notes">
- Hardware is awful
- Revered the Thinkpad
- Same computer to everyone
- From the secretary to the top manager
</aside>
<aside class="hide">
My favorite thing is the hardware, they revered the Thinkpad. They still can't understand that developers needs a minimum of tools. They just give to every one the same computer to everyone with a maximum of antivirus and crypted harddrive and consider the developer has to be happy with it.
</aside>
</section>
<section>
<h3>Internet Explorer</h3>
<img src="img/article_IE_logo_o.JPG" />
<aside class="notes">
- Kingdom of old Internet Explorers
- IT department security politics
- Official browser
</aside>
<aside class="hide">
You also got Internet Explorer. Big companies are the kingdom of olds Internet Explorer. The IT departments politics are always about only Internet Explorer, you know, for security!
</aside>
</section>
<section>
<h3>Choosing a new piece of software...</h3>
<ul>
<li>They have to spend money</li>
<li>One solution to rules them all</li>
</ul>
<aside class="notes">
- Workflow is really corrupted
- Absolutly spend money
- They wan to aquire the technology
- They want the solution be used in every single project
</aside>
<aside class="hide">
A very difficult topic is that the workflow to choose a new piece of software is really corrupted. They absolutly want to spend money to be reassured. That's of course not a great start to choose Open Source. The worse is that as they spent money, they want the solution to be used by everyone and everywhere in the company. We all know that any solution can fit for every single project of a big company.
</aside>
</section>
<section>
<h3>Industrial Workflows</h3>
<img src="img/arrow-diagram.gif" />
<aside class="notes">
- Industrial Workflows
- A diagram like this one in every conference room
- To sum it up, processes are really complex
- The goal is to be able to fit in
</aside>
<aside class="hide">
And finaly, there is the Industrial Workflow. I actualy worked in a company where there had a diagram like this one in every single meeting rooms. All the processes in this companies are huge and be able to fit in is a key of the success.
</aside>
</section>
<section>
<h3>Selling the Web Platform<br> to these "big companies"<br> is not an easy task</h3>
<img src="img/wplogo_transparent_xlg.png" style="background-color: white;" />
<aside class="notes">
- Sell Web UI and JavaScript is not easy
</aside>
<aside class="hide">
You can imagine know that triying to sell Web UI and JavaScript development in these companies is not an easy task.
</aside>
</section>
<section>
<img src="img/Dead-End.jpg" />
<aside class="notes">
- Hipster technology
- Companies workflow
- Leads to a dead end
</aside>
<aside class="hide">
It's often ending here because Hipster technology not fitting in the companies workflow does not go very far.
</aside>
</section>
<section>
<img src="img/Raising-Hope.jpg" />
<aside class="notes">
- Theres is hope
- Also a great show by the way
</aside>
<aside class="hide">
But there's hope! (And it's also a great show by the way)
</aside>
</section>
<section>
<h3>The situation has evolved</h3>
<img src="img/ie6nomore-logo.jpg" />
<br>
<img src="img/Adobe_freaking_amazing_logo.jpeg" height="100" style="vertical-align: middle;" />
drops
<img src="img/apacheflex_fc-1.jpg" height="100" style="vertical-align: middle;" />
<br>
<img src="img/dezeen_Google-logo_1sq.jpg" height="100" style="vertical-align: middle;" />
drops
<img src="img/gwt-logo.png" height="100" style="vertical-align: middle;" />
<aside class="notes">
- Context has evolved
- I6 is finally dead
- There will still be old IE
- At least IE 8 can do a little of HTML 5
- Key concurents has been droped
- Projects still exists as OS project
- No more support is like death sentence
</aside>
<aside class="hide">
First off all, the context has evolved. IE6 is finally dead. Or at least, I haven't seen it for a while and I really hope to never see it again. Flex and GWT which was the most commonly used alternatives was both dropped. Even if both projects still exists as Open Source projects, the drop of support is death sentence from the view of a big company.
</aside>
</section>
<section>
<h3>The magic Keyword has landed</h3>
<img src="img/html5-logo-1.jpg" />
<aside class="notes">
- Magic keyword is appeared
- Transform an hipster technology
- Trendy and shiny thing
</aside>
<aside class="hide">
And the magic Keyword has appeared. Keywords are great to sell software to big companies, they can transform a technology from a geeky unstable one to a trendy shiny thing. And it's exactly what the HTML 5 keyword do for the Web Platform.
</aside>
</section>
<section>
<h3>JavaScript ecosystem has evolved</h3>
<img src="img/JavaScript_Tools_Library_Frameworks.jpg"/>
<aside class="notes">
- I'm here for that today
- The JavaScript development has greatly evolved
- New tools, new frameworks
- Wich allows to comply with heady workflows
</aside>
<aside class="hide">
But most of all, and I'm here for that today, the JavaScript ecosystem has greatly evolved.
</aside>
</section>
<section>
<h3>First you have to enter</h3>
<img src="img/doorway.jpg" />
<aside class="notes">
- You have to enter
</aside>
<aside class="hide">
First of all, you have open the doors of the industrial world.
</aside>
</section>
<section>
<h3>AngularJS</h3>
<img src="img/angularjs.jpg" />
<aside class="notes">
- Perhaps somebody knows
- Huge fan of AngularJS
- Gave a few talks about it
</aside>
<aside class="hide">
And for that, you've got Angular. As perhaps somebody knows, I'm a huge fan of Angular.
</aside>
</section>
<section>
<h3>Whether you like AngularJS or not, it's the key to bring JavaScript development in big companies</h3>
<aside class="notes">
- Why I prefer Angular over other frameworks
- Really good to enter big companies
</aside>
<aside class="hide">
But I will not talk about why I prefer Angular over any other JS MVC framework but why Angular is really good to enter big companies.
</aside>
</section>
<section>
<h3>The following views are NOT my own!</h3>
<aside class="notes">
- To be clear
- Not good developers arguments
- There are not mines
- Those which works in enterprises
</aside>
<aside class="hide">
To be clear, these points are not good developers arguments. And they are not mines. But they are those which works in enterprises.
</aside>
</section>
<section>
<h3>Supported by Google</h3>
<img src="img/angularjs.png" style="background-color: white;" />
<aside class="notes">
- "by Google" power
- Big companies are looking for support
- They can't pay
- At least, there is the leader of Internet behind
</aside>
<aside class="hide">
First, the "by Google" power. As I said before, big companies are looking for support. If they can't pay for support, at least, Angular is supported by a big company which gives references.
</aside>
</section>
<section>
<h3>Full stack framework</h3>
<img src="img/juggling-monkey.jpg" />
<aside class="notes">
- Full stack framework
- Afraid of the so called jungle of JS frameworks
- Hope to simplify
- It's an utopy
- It still works pretty well as an argument
</aside>
<aside class="hide">
Angular is a full stack framework. They are afraid of the so called jungle of JavaScript frameworks. And they hope to simplify that jungle by choosing a single framework to make everything. It's an utopy but it still works pretty well as an argument.
</aside>
</section>
<section>
<h3>Dependency Injection</h3>
<ul>
<li>Structure</li>
<li>Modularity</li>
<li>Testability</li>
</ul>
<br><br>
<h4>Match with Java EE concepts<br>Spring & EJB</h4>
<aside class="notes">
- This one at least is a real argument
- Depdency injection pattern
- It provides structure, modularity, testability
- Reassuring
- Same pattern as majors Java frameworks
- Java developers who handles theses concepts for a while
</aside>
<aside class="hide">
This one at least is a real argument. Angular has dependency injection. It provides structure, modularity and testability which is great features and also reassuring for Java developers which handles theses concepts for a while now.
</aside>
</section>
<section>
<h3>But once inside, it's only the beginning</h3>
<aside class="notes">
- We're in
- Everything remains to be done
</aside>
<aside class="hide">
Well. At this point, we're in, but everything remains to be done.
</aside>
</section>
<section>
<h3>They never have invested in design...</h3>
<aside class="notes">
- Often internal projects with few users
- Don't invest a thing in design
- Let design to a Java trainee
- Usually a disaster
</aside>
<aside class="hide">
These big companies, when they start a new internal project they don't invest a thing in design. Which leads to let the design to Java trainee which is usually a disaster.
</aside>
</section>
<section>
<img src="img/bootstrap.png" />
<aside class="notes">
- We've got Bootstrap
- You probably know it as the most starred project of GitHub
- Best practice is to make a design on top of it
- At least, ables to produce clean webapps
</aside>
<aside class="hide">
But now, we've got Bootstrap. It's not perfect, and of course, every applications looks the same, but at least, Web applications looks clean and it changes the way of seeing webapps.
</aside>
</section>
<section>
<h3>Bring Java developer to (real) JavaScript development isn't easy, but...</h3>
<aside class="notes">
- Bring Java developers to real JavaScript development
- JavaScript is not object
- Weak typed
- Very permissive
- There again, there is tools
</aside>
<aside class="hide">
The second element is to bring Java developers to do real JavaScript development. As JavaScript is not object, weak typed and very permissive langage, Java developers struggle with it. But there again, there is tools.
</aside>
</section>
<section>
<img src="img/jshintjslint.jpg" />
<aside class="notes">
- Many solutions
- Different approaches
- Plug into you IDE
- Have feeback like in Java with the compiler
</aside>
<aside class="hide">
There is many solutions with different approaches, you just have to choose yours. But you have to plug it into your IDE to be able to have good feedbacks while you develop.
</aside>
</section>
<section>
<h3>We've got also Dependency management</h3>
<aside class="notes">
- Used to dependency managment
- JavaScript has its own
</aside>
<aside class="hide">
Java developers are used to dependency management. And now, JavaScript has it's own.
</aside>
</section>
<section>
<img src="img/bower.jpg" />
<aside class="notes">
- Called Bower
- Pretty simple and useful
- It uses Git to download dependencies
- Ables to use directly GitHub
</aside>
<aside class="hide">
It's called Bower. It's pretty simple and useful, it uses Git to download the dependencies directly from GitHub.
</aside>
</section>
<section>
<img src="img/grunt-logo.png" height="200" style="background-color: white;" />
<h2>
<img src="img/gulp.png" height="200" style="background-color: white; margin: 0 20px 0 120px; vertical-align: middle;" />
Build
<img src="img/brunch-logo-napkin.png" height="200" style="background-color: white; margin: 0 20px; vertical-align: middle;" />
</h2>
<img src="img/jake.png" height="100" />
<aside class="notes">
- Most important revolution
- JavaScript industrialisation
- Build tools
- There's few of them
</aside>
<aside class="hide">
But the most important revolution of the JavaScript industrialisation is the build tools. There's few of them. The leader is Grunt even if Gulp is the buzz right now.
</aside>
</section>
<section>
<h3 style="text-decoration: line-through;">"JavaScript is not compiled,<br> it doesn't need to be built"</h3>
<aside class="notes">
- Big mistake
- Made for too long
- Web doesn't need to be built
</aside>
<aside class="hide">
The big error which was made for too long is to think that the Web doesn't need to be built.
</aside>
</section>
<section>
<h3>Grunt</h3>
<img src="img/grunt-logo.png" />
<aside class="notes">
- Main build tool
- Great logo
</aside>
<aside class="hide">
Let's talk some more about Grunt. Yes, it has a great logo!
</aside>
</section>
<section>
<h2>Web optimization</h2>
<h3>No one should anymore copy his source files on a Web server</h3>
<img src="img/automate.jpg" />
<aside class="notes">
- First usage is for Web optimization
- So many operations to perform
- Pass from your source files to a production package
</aside>
<aside class="hide">
The first usage of Grunt is for Web optimizations. There is so many operations you have to perform today to pass from your source files to a production version of your website.
</aside>
</section>
<section>
<h2>Web Deployment<br>in 2014 =</h2>
<h3>
Verifications (JsHint) +<br>
Preprocessors (Sass, Coffee...) +<br>
Minifications (Uglify) +<br>
Image Optim (Imagemin...) +<br>
Concatenations (concat) +<br>
Cache Buster (rev) +<br>
...
</h3>
<aside class="notes">
- Packaging process should look like this
- No way considering deploying with a simple copy
</aside>
<aside class="hide">
In 2014, your build process should look like this. There is no way you could still considering deploying a web app with a simple copy.
</aside>
</section>
<section>
<h3>Grunt can "watch" your files and recompile everything</h3>
<aside class="notes">
- Great feature
- To be able to watch your files
- Run every task when it sees a change
</aside>
<aside class="hide">
One of it's great features is to be able to watch your files and then run every task you want when it sees a change.
</aside>
</section>
<section>
<h3>Welcome preprocessors!</h3>
<h3>for CSS...</h3>
<img src="img/sass-less-stylus.jpg" />
<aside class="notes">
- It opens the doors to preprocessors
- Big enhancement of Web development
- Most commonly used are for CSS
- Almost a must have nowadays
</aside>
<aside class="hide">
It opens the doors of all Web preprocessors. Preprocessors are a big enhancement for Web development. The most commonly used preporcessors are for CSS with Sass Less or Stylus. It's almost a must have nowadays.
</aside>
</section>
<section>
<h3>JavaScript...</h3>
<img src="img/coffeescript_logo.png" height="200" />
<img src="img/typescript-logo-426x188.jpg" height="200" />
<img src="img/es6.png" height="200" />
<aside class="notes">
- Also consider JavaScript preprocessors
- CoffeeScript which I use myself
- TypeScript which is great even if it's made by Microsoft
- Even try EcmaScript 6 with Traceur Compiler
</aside>
<aside class="hide">
But you can now also consider JavaScript preporcessors like CoffeeScript, TypeScript. You can even try ECMA Script 6 with the Traceur compiler from Google.
</aside>
</section>
<section>
<h3>Even HTML!</h3>
<img src="img/Haml_1-5_logo.png" height="200" />
<img src="img/jade.png" height="200" />
<aside class="notes">
- Also process your HTML
- Handle simpler and more meaningul files
</aside>
<aside class="hide">
Finally, you can also process your HTML to handle simpler and more meaningful HTML files.
</aside>
</section>
<section>
<h3>Too much Grunt configuration?</h3>
<aside class="notes">
- Afraid of the amount of Grunt configuration
- I'm one of them
</aside>
<aside class="hide">
For those who are afraid of the amount of Grunt configuration, and I'm one of them...
</aside>
</section>
<section>
<h3>There is also a solution, he's called Yeoman</h3>
<img src="img/yeoman-logo.png" />
<aside class="notes">
- Once again a solution
- Yeoman is a scaffolding solution
- Will initiate your project and you Gruntfile
</aside>
<aside class="hide">
There is, once again, a solution. Yeoman is a scaffolding solution which will initiate your project with a very complete Gruntfile.
</aside>
</section>
<section>
<h3>Grunt will also run your tests!</h3>
<img src="img/unit-test.jpg" />
<aside class="notes">
- Also be able to run the tests
</aside>
<aside class="hide">
Grunt will also be able to run your tests.
</aside>
</section>
<section>
<h3>Unit Testing JavaScript?</h3>
<h2>YES!</h2>
<aside class="notes">
- Very good testing framework for JavaScript
- Tests are really important to handle browsers differences
- Most used is called Jasmine
</aside>
<aside class="hide">
Yes, there is very good testing in JavaScript now. The most commonly used framework is called Jasmine.
</aside>
</section>
<section>
<h3>With Jasmine</h3>
<img src="img/JASMINE.jpg" height="500" />
<aside class="notes">
- Sorry for my little joke
</aside>
<aside class="hide">
Oops, not this one.
</aside>
</section>
<section>
<h3>No, this one</h3>
<img src="img/jasmine-logo.png" />
<aside class="notes">
- This logo
</aside>
<aside class="hide">
Yes, this one.
</aside>
</section>
<section>
<h3>Or with that one from<br> the Node.js community</h3>
<img src="img/mocha.png" />
<aside class="notes">
- My prefered one
- The one from the Node.js community
- Also work in browsers
- Particularity is to do nothing
- External modules to do the rest
</aside>
<aside class="hide">
But it's not my prefered one. I really enjoy Mocha which is the test framework built by the Node.js community which also works for the Web. It has a particularity, it does nothing. It provides only the tests structure and allows external modules to do the rest.
</aside>
</section>
<section>
<img src="img/chai-logo.png" />
<img src="img/chai.png" />
<img src="img/sinon.png" />
<aside class="notes">
- Chai for assertions
- Very beautiful assertions
- Should, expect and assert
- Complete with Sinon JS
- Brings spys, stubs and mocks
</aside>
<aside class="hide">
Like the assertions which are handled, for example, by Chai JS which allows to make very beautiful assertions.
You can also complete with Sinon JS which brings spys, stubs, mocks and everything you need for a really complete test environment.
</asides>
</section>
<section>
<img src="img/karma.png" height="150" />
<aside class="notes">
- Not finished with test tools
- Web tests needs to be run in a browser
- Karma can handle your browser
- Run your tests and gather the results
</aside>
<aside class="hide">
And it's not finished with the test tools. There is also Karma which will watch your files, run your tests...
</aside>
</section>
<section>
<h3>In every browsers!</h3>
<img src="img/browsers.png">
<aside class="notes">
- In several browsers
</aside>
<aside class="hide">
...in every browsers you configure.
</aside>
</section>
<section>
<h3>And produce reports</h3>
<ul>
<li>In the console</li>
<li>In HTML files</li>
<li>In JUnit compatible format</li>
<li>With coverage!</li>
</ul>
<aside class="notes">
- Producing all kinds of reports
- Test reports
- Coverage
- Compatible with all the Java tools
</aside>
<aside class="hide">
It's also capable of producing all kinds of reports and coverage which will be compatible with all the Java tools.
</aside>
</section>
<!--<section>
<h3>Of course, you can put Karma in the Grunt workflow</h3>
<aside class="notes">
Of course, Grunt, Karma, Mocha are a big sets of tools which can work together.
</aside>
</section>-->
<section>
<h3>You can fit your JavaScript project in Jenkins & Sonar</h3>
<h2>
<img src="img/js.jpg" height="120" style="vertical-align: middle;" />
+
<img src="img/grunt-logo.png" height="120" style="background-color: white; vertical-align: middle;" />
=>
<img src="img/jenkins.png" height="120" style="background-color: white; vertical-align: middle;" />
&
<img src="img/sonar-logo.jpg" height="120" style="vertical-align: middle;" />
</h2>
<aside class="notes">
- All theses tools can be orchestrated by Grunt
- Produce all the reports you need
- Fit in industrial processes
- Plug your project Jenkins for CI
- Load you reports in Sonar to have quality dashboard
</aside>
<aside class="hide">
All theses tools I talked about can be orchestrated with Grunt. They can produce all the reports you need to fit in the industrial processes of big companies. You can plug your project in Jenkins for continuous integration and Sonar for quality reports.
</aside>
</section>
<section>
<h3>JavaScript projects can finally fit in Industrial workflows</h3>
<aside class="notes">
- Build, tests, reports
- JavaScript project fit in industrial workflow
</aside>
<aside class="hide">
You have, build, tests, reports, your JavaScript project can fit in the Industrial workflow.
</aside>
</section>
<section>
<img src="img/businessman-thumbsup.jpg" />
<aside class="notes">
- Your business man should be happy
- Perhaps no more looking at you as a dangerous hipster
</aside>
<aside class="hide">
At this point, your business man should be happy and perhaps not looking at you as a dangerous hipster!
</aside>
</section>
<section>
<h2>Thank you!</h2>
<h2>
<a href="https://twitter.com/Swiip" style="color: white;">
<img src="img/Twitter_logo_blue.png" style="height: 80px; vertical-align: middle; border: none; box-shadow: none; background-color: transparent;" />
<img src="img/swiip.jpg" style="vertical-align: middle;" />
@Swiip
</a>
</h2>
<aside class="notes">
- Thank you
- Any questions
</aside>
<aside class="hide">
Thank you! Any questions?
</aside>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.min.js"></script>
<script>
// Full list of configuration options available here:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
theme: Reveal.getQueryHash().theme, // available themes are in /css/theme
transition: Reveal.getQueryHash().transition || 'linear', // default/cube/page/concave/zoom/linear/fade/none
// Parallax scrolling
// parallaxBackgroundImage: 'https://s3.amazonaws.com/hakim-static/reveal-js/reveal-parallax-1.jpg',
// parallaxBackgroundSize: '2100px 900px',
// Optional libraries used to extend on reveal.js
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, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true, condition: function() { return !!document.body.classList; } },
{ src: 'plugin/notes/notes.js', async: true, condition: function() { return !!document.body.classList; } }
]
});
</script>
</body>
</html>