Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Quality from the start
Search
Filipe Freire
February 15, 2018
Programming
0
160
Quality from the start
Talk about software quality and testing for students, given at Helloworld Conference 2018.
Filipe Freire
February 15, 2018
Tweet
Share
More Decks by Filipe Freire
See All by Filipe Freire
Deep Testing
filipe
0
120
Finding Tranquility
filipe
0
120
Quality Foundations
filipe
0
130
Tacit CSS Framework
filipe
0
420
Elegant Objects and Cactoos
filipe
0
360
Tacit
filipe
0
190
Waiting is boring
filipe
0
690
You don't need a DevOps to "be DevOps"
filipe
0
360
Other Decks in Programming
See All in Programming
alien-signals と自作 OSS で実現する フレームワーク非依存な ロジック共通化の探求 / Exploring Framework-Agnostic Logic Sharing with alien-signals and Custom OSS
aoseyuu
2
220
Go言語はstack overflowの夢を見るか?
logica0419
0
520
CSC509 Lecture 05
javiergs
PRO
0
310
コードとあなたと私の距離 / The Distance Between Code, You, and I
hiro_y
0
190
Pythonに漸進的に型をつける
nealle
1
120
Foundation Modelsを実装日本語学習アプリを作ってみた!
hypebeans
1
120
ソフトウェア設計の実践的な考え方
masuda220
PRO
4
630
その面倒な作業、「Dart」にやらせませんか? Flutter開発者のための業務効率化
yordgenome03
1
140
技術的負債の正体を知って向き合う
irof
0
230
Devvox Belgium - Agentic AI Patterns
kdubois
1
140
XP, Testing and ninja testing ZOZ5
m_seki
3
810
Catch Up: Go Style Guide Update
andpad
0
240
Featured
See All Featured
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
55
3k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
34
2.5k
How To Stay Up To Date on Web Technology
chriscoyier
791
250k
What’s in a name? Adding method to the madness
productmarketing
PRO
24
3.7k
GraphQLとの向き合い方2022年版
quramy
49
14k
Product Roadmaps are Hard
iamctodd
PRO
55
11k
Large-scale JavaScript Application Architecture
addyosmani
514
110k
Learning to Love Humans: Emotional Interface Design
aarron
274
41k
BBQ
matthewcrist
89
9.8k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
31
9.7k
Mobile First: as difficult as doing things right
swwweet
225
10k
How GitHub (no longer) Works
holman
315
140k
Transcript
Quality from the start Filipe Freire 15 February 2018
Learner, tester, developer, husband 2.5y work as a “coding” tester
1y work as a developer OSS contributor Quick intro Currently @ 2
“Job application, public <service>” Ex.: hospital Story time 3
4
5
6
“Inspect the code!” “Use the Dev-tools!” Nope. 7
8
The pizza problem #1 9
1st pizza: 2nd pizza: The pizza problem #2 10
In the team I’m part at >10mil messages/day +
tons of data & logic and flows If something fails for 10 mins: 11
What if : Your bank’s software fails? Your doctor’s medical
device fails? Your country’s defences fail? 12
“It’s the user!” “It’s the tester!” “It’s the developer!” 13
Who’s to blame?
Why do we test? 14
“To verify something can work” –James Bach & Michael Bolton
15
What prevents software from working? 16
–Yegor Bugayenko “A software bug is an error, flaw, failure,
or fault in a computer program or system that causes it to violate at least one of its functional or non-functional requirements.” 17
“ (Testers are) the headlights of a project”! –James Bach
Testers dispel the illusion your code is good. Our main job: find and report tons of bugs using any means necessary 18
Remember “who’s to blame”? Answer: anything and everything between
our code (incl.) and the user 19
–Pedro Tavares (@ordepdev) “No one is perfect, neither our code,
but what matters most is our software craftsmanship attitude of making sure that our code works properly.” 20
Everyone makes their own shared bed. “What can I
do help make a better bed?” 21
-9999. “Do you know the value of your tool?” -
Tooling! 22
BTW, the following, credit goes to: http://www.yegor256.com/ 2015/06/08/deadly-sins- software-project.html 23
1. Can I be sloppy? - Anti-Patterns! 24
- Anti-Patterns! God objects Temporal coupling Magic numbers Utility classes
NULL references ORM… really? Poltergeists Lasagna code Spaghetti code Shotgun surgery Error hiding Ravioli code Macaroni code Be skeptical. Read. Learn. Google DuckDuckGo it. 25
2. How do I keep track of stuff? 26 -
Traceability!
Use tickets. Reference them. Don’t hit delete. 27 - Traceability!
Use tickets. 28 - Traceability!
Use tickets. 29 - Traceability!
Reference them. 30 @filipe: asdfasdf. @roberto: add function discussed yesterday
@bob: - Traceability! @agnes: fix problem.
Reference them. 31 @filipe: #3 - add login page style
rules @roberto: #7 - refactor nurse page unit tests @bob: #2 add how-to-build info - Traceability! @agnes: #4 - fix report input warning
32 @rita: #12 - add patient list as table @ana:
#13 - delete patient list Don’t hit delete. - Traceability!
3. How can I package my work - Release and
version! & not work nonstop? 33
“put your work in a zip and send an email
to the teacher at midnight, on the last day to deliver” - Release and version! 34
“some work done: tell a bot or script to create
+ publish a package. Repeat.” - Release and version! 35
- Release and version! 36 Best advice here: learn!
4. “How can I keep my stuff tidy all the
time?” - Static-analysis! 37
- Static-analysis! 38
Find some static analysis software for the language you code…
Then, make it fail your builds, always. - Static-analysis! 39
5. What are my numbers? - Coverage! 40
Do everything necessary to put this badge on your project
- Coverage! 41
- Coverage! 42 You’ll need: - Unit tests (Learn and
make’em) - Configure some coverage lib - Paste the badge on README
- Coverage! (What does the badge tell me?) “High coverage
is not a guarantee of high quality. (…) But, unknown coverage is a clear indicator of maintainability problems.” –Yegor Bugayenko 43
6. “What does your stuff do?” - Document! 44
45 - Document! The tip here is: Write down, clearly,
everything a user would need to know to use your software. Bonus point: when report time comes, you’ll have some sections ready :-)
Best-case scenario Year 1: “Ana and Miguel do class assignment
for X: it’s maintainable, well documented” A + M Work 46
Best-case scenario Year 2: “Rui and Tiago do class assignment
for X: they pick were Y1 colleagues left off and still deliver maintainable, well documented work” A + M Work R + T Work 47 +
Best-case scenario Year 3: “Rita and Marta do class assignment
for X: they pick were Y2 colleagues left off and still deliver maintainable, well documented work” A + M Work R + T Work R + M Work 48 +
Worst case scenario Maintainable garbage Still better than most real-life
scenarios :-) 49
And like in OSS: You’re not just setting the bar
for the next year student on your class. 50
Wrap-up 51
Example: Porto Testers Meetup 52 Learn, share ideas & knowledge.
Go out there! Community!
Pst… There’s more @Porto! 53
Thank you. Questions? filfreire filrfreire filfreire.com 54 Follow me @