RubyFlow : The Ruby Community Blog

Home   Submit   Sign Up   Log In   leaders   Twitter   RSS Feed  

markoa — 24 posts

Unmet data or configuration dependencies are a frequent cause of unexpected test failures, followed by long debugging. This post discusses a few examples.
Inspired a by Stack Overflow thread, I discuss helping yourself by avoiding test case clutter.
I just updated admin_view to work with Rails 4. It's a small code generator that can create a nice Bootstrap-friendly admin interface for existing Rails models. I find this useful because admin interfaces I work with almost always need to be customized, and this gets me to that point quickly. More background here.
I wrote a blog post on managing externals in your Ruby tests. It includes tips for managing time conditions, avoiding HTTP requests and testing an OAuth flow.
The ease of testing controllers is inversely proportional to how decoupled they are from the rest of the app. Read some examples in this post on antipatterns in testing Rails controllers.
The biggest issues with model tests are usually a reflection of application design.
I just published the first post in a series about Rails testing antipatterns. It's about fixtures and factories.
Capistrano 3 introduced a whole new DSL and many changes under the hood. Here's an upgrade guide using a real Capistrano 2 script as an example.
Here's a quick guide to using multiple Gemfiles in the same branch. Might be handy when you're migrating and testing against a new version of a framework or important gem.
I crunched some numbers on Semaphore and published a chart showing the distribution of rubies used in commercial projects.
It's very simple: just use pusher-fake.
Say you're using Jasmine, and you're writing CoffeeScript in a Rails app. Here are some tips for running those tests in CI environment.
So you've just picked up a rather large Rails codebase that has not been updated for a while. The tests are missing. The client is expecting new features. How do you manage all that?

This two-part article offers some tips: from communicating effectively and exploring the code to adding tests and shipping new features.
Applying some principles from functional programming can simplify your code. Here's a short walkthrough based on a Rails helper.
If you'd like to internationalize a Rails app with a simple homemade interface, you can use database-backed FastGettext and store your translations in version control as a Yaml file.
ActiveRecord and Azure
Here's what you need to know if you find yourself developing a Rails app that is using an MSSQL database hosted on Azure.
A while ago we asked for some beta testing love, and the response was tremendous. Today Semaphore, a hosted continuous integration app for Ruby, launched to public.
I followed John Carmack's advice and discovered that static code analysis is the next step (after BDD) if you care about your craft.
Semaphore, a new continuous integration app for Rails projects, is looking for beta testers. It can import any GitHub repository, while the set up & build process is made completely automatic.
How do you call your CoffeeScript code in Rails? I just posted a discussion and a solution with the goal to keep it simple. Comments are totally welcome.
admin_view is new kid on the Rails admin interface block. It generates a small chunk of opinionated scaffold-like code with a simple search form on a paginated, column-sortable listing. Read more on the announcement blog post.
We just published a big list of gems, plugins and APIs that we use in our work. Hoping more other companies and individuals will share theirs too.
I made a generic Sinatra app coming-soon that shows a pre-launch page and collects emails. Also includes an admin view and CSV export.
After being only on GitHub for too long, I'm introducing a freshly cut r2flickr, a gem which builds on the old rflickr, a close reproduction of the Flickr API as it is published.