#testing
9 posts
2026 - February
1 post2018 - April
1 post2017 - October
2 posts2016 - October
1 post2015 - December
2 posts2009 - May
1 post2009 - February
1 post2026 - February
1 postIntegration Tests in a Monorepo | Behind The M.Akita Chronicles
How a monorepo running three apps that share a filesystem uses a dedicated integration environment, DevCache, rsynced production data, and preflight checks to catch the bugs unit tests never see.
2018 - April
1 post[SmallTips] Running GitLab CI Runner Locally
GitLab CI Runner uses `.gitlab-ci.yml` to reproduce failing server jobs locally through Docker, speeding up diagnosis. The tradeoff is starting over without cache or artifacts.
2017 - October
2 posts[Beginner] Long live PhantomJS, let's use Chrome Headless now
Fabio shows how to replace Poltergeist and PhantomJS with Selenium WebDriver and Chrome Headless in RSpec and Capybara. The setup changed, but the existing feature specs ran without alterations.
How NOT to zero out your Pusher development quota
Pusher Fake keeps Rails development and tests connected to a local server without using Pusher's free quota. Fabio explains the setup with Foreman, matching variables, and RSpec.
2016 - October
1 postSharing models between Rails Apps - Part 1
I extracted stable Central model logic into Concerns in a testable RubyGem, moved the specs with almost no changes, and concluded it works well for secondary read-only apps.
2015 - December
2 postsEx Manga Downloadr - Part 5: Making it more robust!
MangaFox timeouts expose a flaw in Ex Manga Downloadr’s Workflow. The author uses Task.Supervisor and limited retries to catch HTTPotion errors, leaving GenServer refactoring as technical debt.
Ex Manga Downloadr - Part 4: Learning through Refactoring
Refactoring Ex Manga Downloadr replaces six repeated blocks with macros, improves Floki usage, and uses online tests to validate parsers. The project reaches version 1.0.0 with two fewer files.
2009 - May
1 post[Off-Topic] The 5 Team Dysfunctions in Code
Five team dysfunctions appear in anti-patterns such as null checks, duplication, untested code, and hard-to-understand solutions. Isolated techniques cannot fix a command-and-control organization.
2009 - February
1 postTranslation: Flaccid Scrum
Martin Fowler's translation shows how adopting Scrum without technical practices can leave code flaccid. Fabio emphasizes testing, refactoring, frequent integration, and collective ownership.