Llevo más de un año escribiendo código con IA. Claude Desktop fue la primera herramienta seria que usé — y por eso construí Rails MCP Server y nvim MCP Server, para darle acceso a leer mi código y proponer cambios. Con Claude Code el proceso se simplificó. Pero descubrí algo: la investigación, la planeación y cualquier cosa que generara documentos largos para leer en la terminal no eran cómodos. Entonces volvía a Claude Desktop y hacía copy/paste entre las dos aplicaciones (sí, recuerd0 estaba en medio, pero esa es otra historia). El brincar entre apps no me molestaba. Pero un día se me ocurrió que debía haber una mejor manera de hacer esto. Esa mejor forma es Fragua: una app de Rails que orquesta agentes de IA a lo largo de todo el arco de construir una app de Rails — investigación, plan, foundation, spec, código, pull request — con el trabajo visible todo el tiempo. Antes de empezar, miré bolt.new y Lovable. Son impresionantes y, para muchas personas, lo correcto. Pero los sentí como vibecoding y están construidos sobre stacks que no uso. Por eso Fragua habla Rails nativamente — Hotwire, Solid Queue, Minitest, maquina_components — no porque sea mejor, sino porque es el lenguaje que mis clientes y yo ya hablamos. Me importa la calidad, la consistencia y una mejor forma para que los equipos técnicos trabajen con IA. Pero también la conducta de los agentes — observable y registrada, para poder leer después qué pasó. Y BYOK: tu API key, tu cuenta, tu factura. Fragua nunca proxea tu uso. Está en beta privada en fragua.app. Si tienes una idea pero no eres developer, las fases iniciales (research, plan) sirven solas hasta donde necesitas a alguien que construya.

Chapter 5 of Minitest Rails is now live 🚀✨ I walk you through the following in this new chapter: - Recipe scaffold - Your first model test with TDD - Integration tests - Git commits after a green test run (a habit worth keeping in real projects) minitestrails.com/guide/your…

Refind Self Una experiencia cortita que quiere contar una historia e intenta ser un minitest de comportamiento, no puedo exigirle mucho 7 ovejas acariciadas/la cantidad de veces que intente tirarme del edificio por si cambiaba algo... como esto también lo tiene en cuenta?? D:

If you're using Rails defaults and Minitest, I wrote a complete walkthrough showing the exact setup, helper methods, and system tests: minitestrails.com/blog/testi… 11/11

#Rails Testing Tip ✨ Testing Auth0 login in Rails with Minitest is trickier than most authentication systems. Why? Because your tests shouldn't actually redirect to Auth0. 🧵 1/11

If you refuse to read content just because the author used AI, you’re missing the point entirely. Lately, I’ve been using AI to help write my tech blogs and chapters for Minitest Rails guide. ​And honestly? I don't care if that makes some people raise their eyebrows 1/n 🧵

@coolprobn Ruby on Rails consultant from Nepal, maintains a guide on Minitest Rails (minitestrails.com). This guide is helpful to both new and experienced Rails developers; Great work Prabin,

Step 3: Automate manual steps Finally, I write automated tests using Minitest as I now know what steps to automate. I normally write integration tests for these type of tests but system test is best for beginners since you can view tests running live in the browser. 🧵 5/n

Stop fighting the framework with a bloated testing stack. Rails defaults are all you need for a blazing-fast test suite. Master Minitest, Fixtures, and Capybara and drop all unnecessary gems. Keep it Simple, Stupid! minitestrails.com/guide/test…

We’ve rolled out optimizations for NeetoCI by introducing a new block architecture system that significantly reduces the time taken by CI tests across all Neeto apps. The CI run for @NeetoCal and @NeetoForm used to take around 18–20 minutes. That has now been reduced to 5–7 minutes. Here’s a quick presentation with a detailed overview. vishal24367.github.io/ci-tes… Shopify's minitest-distributed github.com/Shopify/minitest-… helped in parallelizing the test run and cutting down the time take. This gem has only 13 stars on GitHub. I deserves more love.

Roadmap update for minitestrails.com ✨ I’m swapping the next two chapters to keep the momentum moving: 3⃣ Minitest Tool Ecosystem (Next) 4⃣ Testing Strategy 5⃣ Your first Test This gets the theory out of the way so we can dive straight into real world examples!

Use minitest!

A 45-minute Rails test suite is not normal. Minitest fixtures can be boring, simple, and fast and that’s exactly the point. Sometimes the best Rails stack is just the default Rails stack.

Why do we keep getting this "I converted from RSpec to Minitest and got X times faster" posts when the actual performance story is going from factories to fixtures. EVERY SINGLE TIME!

.@nicodhnr could've been an Oscar-winning actor. Instead he built @minitap_ai, the QA tool mobile teams have needed for years. His team just launched minitest – a fully managed AI QA engineer for iOS and Android that runs entire test suites end to end, catches the bugs users would hit, and hands you the fix immediately. No authoring or maintenance required. Hollywood's loss is every mobile team's gain.

I said, I was running MiniTest in parallel: x.com/igor_alexandrov/status…. RSpec parallel executors all are pain in the ass.

It seems you were running RSpec single-core and you're running Minitest in parallel. Or is that not the case? What would the time difference be if you ran both in parallel?

Glad to read this! I've been using only Minitest for years and I'm so happy with it.