This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathrails_4_post_mortem.html
109 lines (71 loc) · 2.74 KB
/
rails_4_post_mortem.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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Rails 4 Post Mortem</title>
<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="lib/reveal.js/css/reveal.min.css">
<link rel="stylesheet" href="lib/reveal.js/css/theme/night.css">
<link rel="stylesheet" href="lib/template.css">
<!-- For syntax highlighting -->
<link rel="stylesheet" href="lib/reveal.js/lib/css/zenburn.css">
<!-- If the query includes 'print-pdf', include the PDF print sheet -->
<script>
if( window.location.search.match( /print-pdf/gi ) ) {
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = 'css/print/pdf.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
}
</script>
<!--[if lt IE 9]>
<script src="lib/reveal.js/lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<div class="slides" id="content">
<section data-markdown
data-separator="==="
data-vertical="---"><script type="text/template">
# Rails 4 Post Mortem
What can we learn from the upgrade to Rails 4
===
## Tests
---
### Some critical features aren't tested
* More routing tests (verbs, permalinks, parameters, SP*, I18n)
* More API tests (XML)
* Critical paths (Account activation, password reset): The current scenario have been tested by hand and are not covering enough
---
### More human tests?
* The dedicated server has not been used
* Who should make live tests?
===
## Maintenance
* More people **(live!)**
* Non regression **(live!)**
---
### Where do bugs come from
* Check what is the weakest layer of our application (models, controllers, views)
* Improve test coverage for that layer in priority
---
### Maintainability
* Some bugs were fixed multiple times because changing one part of the code made an other thing break *(ex: Tire and his infamous callback hell)*
* Decrease complexity of the application in order to improve maintainability
===
## Upgrading gems
* Reduce the number of different gems used (dead code, gem redundancy)
* Upgrade gems more often so that we don't have to upgrade them all at once
</script></section>
</div>
</div>
<script src="lib/reveal.js/lib/js/head.min.js"></script>
<script src="lib/reveal.js/js/reveal.min.js"></script>
<script src="lib/jquery/dist/jquery.min.js"></script>
<script src="config.js"></script>
</body>
</html>