home.social

#rspec — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rspec, aggregated by home.social.

  1. ## Please Don't Nerf RubyLang Because #StyleGuides

    Ruby has made some internal changes that remind me of the changes #RSpec made to clean up internals but uglified the code & made certain features simply stop working as expected.

    Removing `foo rescue nil` is an exmaple. Some edge cases make this antipattern useful; replacing a one-liner with a complex method/chain is annoying. Mindful chainsaw-juggling gave expert #Rubyists superpowers. Not trusting power users is red #Kryptonite for code.

  2. Since last toot yesterday I cracked open a barrel of #Rubocop plugins – this really is the most ergonomic linter I've used 🤩 – and made a lot of headway tidying up the #RSpec tests.

  3. Hey #RubyFriends (and other friends too) 👋 I shipped a big change to my #RSpec book yesterday; here's a post about what's new and what's next. I appreciate your support! everydayrails.com/2025/09/16/r

  4. Hey #RubyFriends, I haven't talked much #Ruby this summer. Life's been full, and I don't write much in my favorite language at my day job right now. But I am very close to (finally!) wrapping up the current edition of my #RSpec book. One more chapter to go! leanpub.com/everydayrailsrspec/

  5. @thoughtbot oh, W-O-W! I never realized before, but #PaperTrail was enabled in our specs. After disabling that and logging, one of our core model #rspec specs went from 6m45s down to 4m15s, or almost 2m30s faster.

    Remember, this is for a single file! Our specs'll fly! Thanks a bunch, @thoughtbot !

  6. 🤔 random thought—does DHH's recent "system tests are dead" proclamation open the door to ViewComponents (or Phlex, or ?) being stock Rails features? I like ViewComponents because I can test UI things without the browser overhead—even if I only use a component once in my whole app. #RubyOnRails #RSpec #ViewComponent #phlex

  7. If you'd like any of these, er, "classic" for just the price of posting, let me know. I think they'd be about £3 to send inside the UK, each. Please only bother if you'd personally like to own it/them - if you'd just plan to flip them then it really wouldn't be worth your while!!

  8. @ruby_discussions Huh. I've migrated from #solargraph to #Ruby #LSP (because LSPs rule), but this might be a game changer.

    #RSpec LSP when?

  9. New post, sharing it here first! Some notes on using AI for the boring parts of software development. In my case, that meant migrating a #RubyOnRails test suite to #RSpec with help from GitHub Copilot. everydayrails.com/2024/03/13/m #AI #programming #githubcopilot #therobots

  10. Fullstack разработка: создаём MVP – путь от технического задания до интеграции

    В работе описана смоделированная ситуация по разработке простого web-приложения на заказ. Для приложения за основу взят фреймворк Ruby on Rails 7 с фреймворком Hotwire и СУБД PostgreSQL. Описание процесса разработки разбито на этапы проектной деятельности, максимально приближенной к жизненному циклу web разработки по методологии Agile. Для максимальной реалистичности в описании упомянуты всевозможные проблемы, которые могут приводить в ступор начинающих Ruby разработчиков. В задачу публикации входит максимальное погружение читателя в процесс разработки. Поэтому работа насыщена ссылками на лучшие образцы методических материалов для экосистемы RoR 7.1 + Hotwire. Любая реальная разработка сопровождается рядом организационных мероприятий, которые распределяются между разработчиками, аналитиками, тестировщиками и DevOps. В заказных разработках часто всё делает один человек. Вот для таких разработчиков, которые хотят всё знать, и предназначена данная статья. Поэтому здесь вы также найдёте дополнительные сведения об особенностях тестового покрытия fullstack разработки, полноценное решение по документированию Rest API, подробное описание процесса докеризации приложения, и инструкцию по использования GitHub Actions по методологии Continuous Integration.

    habr.com/ru/articles/781940/

    #ruby_on_rails #github_actions #dockercompose #hotwire #agile #development #rspec #capybara #bootstrap #JSight

  11. @ervan Without changing your actual #RSpec or #CI setup, you can create multiple #Rake tasks to run specific tags or spec files. Then use #gnuparallel (or `parallel` from #moreutils) to run the tasks on multiple CPUs or cores. For GNU, see the `-j`, `--use-cores-instead-of-threads`, and `--use-sockets-instead-of-threads` flags.

    You can also use subshells or background tasks for OS allocation in #bash, #zsh, or #fish. Also, consider threading without a GIL on #TruffleRuby.

  12. #CrystalLang comes with its own version of #RSpec built in. However, I can't seem to find a Crystal equivalent for #CucumberBDD, although I've heard anecdotally that Turnip (which embeds #GherkinSyntax into RSpec) works even if it lacks some of Cucumber's full feature set. What do Crystal programmers use as a drop-in replacement or alternative implementation for #RubyLang Cucumber?