Another good case is a Test handler to be used in a test environment. A Test handler would be a simple and effective replacement for all the stubs and mocks across our application spec suite. Also, it will ensure no real socket connection is performed outside our application when our test suite is running.
Non-Deep querying
The support for Non-Deep queries is another long awaited feature. You can now skip deep queries for thin providers passing the `:referral => false` option. …
- Signal vs. Noise: Where are the great UI teachers and consultants?
- ZURB: Who Are Your Customers: Elephants, Rabbits or Deer?
- Dima Sabanin: "If someone asks you, "Who is that guy?" then you probably won't waste your breath..."
- Practicing Ruby: Issue #17: Interesting Ruby Hacker-Writers
- Videos related to 'Ruby on Rails - Part 1: Hello World': Computerized Voting Machines: Who is Counting your Vote?
- How Software is Built: Interiew with Denis Lussier - Co-Founder - CTO - EnterpriseDB
Make auto-activation of Test::Unit integration more resilient. This change is specifically to cope with the nasty re-defining of classes that is done by the minitest-spec-rails gem. Fixes issue #143 . Thanks to @ tubaxenor for reporting.
Safer restoration of stubbed method visibility. Fixes issue #141 . Thanks to Aman Gupta .
Ensure Mockery instance gets reset even if exception raised. Fixes issue #144 .
Adapt Mocha acceptance tests …
As I mentioned in my previous post , there's been some recent confusion over which versions of Mocha are compatible with which versions of Rails . In this post, I explain how to use Mocha with Rails and Test::Unit.
Unfortunately due to Rails relying on Mocha & Test::Unit internals, there is a problem with using recent released versions of Rails with the latest version of Mocha and recent versions of the Test::Unit gem . You may see errors like these:
- Blog - James Mead: Using Mocha with Rails 3 and MiniTest
- A Fresh Cup: Double Shot #1011
- Ruby Inside: The Past 2 Weeks in Ruby: 1.9.3-p286, JRuby 1.7RC2, Sidekiq Pro and Much More
- New Relic: Making the Move to Rails 3
- Giles Bowkett: Rails, Ruby, And Type-Checking
- RailsTips by John Nunemaker: An Instrumented Library in ~30 Lines
…'spec/factories' g.assets false g.helper false end
end end
Here, we're telling Rails when generating models, controllers, etc. for your engine to use RSpec and FactoryGirl, instead of the default of Test::Unit and fixtures
After this, you can start writing specs with FactoryGirl factories and integration specs ( inside the spec/features directory ) with Capybara. Have fun testing!
- giant robots smashing into other giant robots: This week in open source
- Darwinweb: Testing ThinkingSphinx with Test::Unit and Transactional Fixtures
- Ruby Fleebie: Review of some testing tools for ruby
- casperfabricius.com: Launch: bog.nu
- Engine Yard Developer Blog: Continuous Deployment with Appboy
- DigitalHobbit: It's been a while...
…'spec/factories' g.assets false g.helper false end
end end
Here, we're telling Rails when generating models, controllers, etc. for your engine to use RSpec and FactoryGirl, instead of the default of Test::Unit and fixtures
After this, you can start writing specs with FactoryGirl factories and integration specs ( inside the spec/features directory ) with Capybara. Have fun testing!
- giant robots smashing into other giant robots: This week in open source
- Darwinweb: Testing ThinkingSphinx with Test::Unit and Transactional Fixtures
- Jason Seifer: Rake Tutorial
- Ruby Fleebie: Review of some testing tools for ruby
- casperfabricius.com: Launch: bog.nu
- Engine Yard Developer Blog: Continuous Deployment with Appboy
The next important change is that the Cheffile included with Test Kitchen no longer specifies the apt , yum , build-essential , git and rvm cookbooks. The existence of these cookbooks in the Cheffile caused " Cheffile and Cheffile.lock are out of sync" errors from Librarian when Test Kitchen assembled the cookbooks. Also, the versions of those cookbooks were pinned to releases from several months ago, which had their own bugs fixed. Test Kitchen has its …
html-pipeline: Chainable Content Filters - New gem from GitHub.
Testacular - Test runner for JavaScript with built in Mocha and Jasmine support, among other things.
The Silver Searcher - "An attempt to make something better than ack, which itself is better than grep."
- giant robots smashing into other giant robots: Giving thanks
- Ruby Inside: This Week in Ruby: JRuby 1.7.0, Passenger 4.0b1, Ruby 2.0 Feature Freeze
- James on Software: Moving On
- Hobo Blog: Hobo 2.0.0.pre1 released
- RailsCasts: #390 Turbolinks
- Giles Bowkett: Ryan Davis, You Are An Idiot, A Liar, Or A Fool
Join us this Saturday, October 27, for pyArkansas . Now in its second year, pyArkansas is a free one day conference for Arkansas and the surrounding region. Anyone interested in learning about all things Python is invited to come listen, give presentations and meet other members of the Python community.
Sessions include:
* Getting Started with GeoDjango
* An Introduction to Test Driven Development in Python
* REST-ful APIS with Flask and MongoDB
* Python for Humans
- DevChix: PyArkansas: Small town, big tech!
- amazing development: Code reviews work
- Positive Incline: PathTo for Python gets a JSON-capable HTTP client
- Joe Fiorini: My Top CodeMash Sessions
- Coding Horror: How to Write Without Writing
- Transcending Frontiers: Positions available: Ruby Developers
Help us Test the Social API with Facebook Messenger for Firefox - I would, if I used Facebook. Here's to Tent integration.
chruby - Another simple alternative for switching ruby versions on the fly.
Benchmark Your Bundle - Simple script to figure out which of your gems is taking the longest to load.
jq - "Like sed for JSON data."
Coalmine - Another cloud-based exception tracking service.
JavaScript for Bootstrap Form…
- ZURB: Read Receipts and User Views In Social Products: Are They Necessary?
- carpeaqua by Justin Williams: Texture
- amazing development: Android scripting environment supports JRuby
- Ruby Inside: JRuby 1.6.0 RC1 Released: JRuby Gets All 1.9.2 On Us
- Engine Yard Developer Blog: JRuby on Windows
You Have to Test For Every Device
This is precisely why responsive design makes sense. You can't possibly test for every device and browser out there. After all, HTC has some 12 different screen size and resolution combinations on Android. And that's just one product line! What about Acer, Motorola, LG, Sony ... well, you get the idea. Conservatively, there are some 6,500 web-enabled devices out there.
We keep small sampling around the office that we test — …
- ZURB: Responsive is the Mobile Web of Tomorrow
- ZURB: The Need for a Responsive Retail Experience
- Merbist: Controlling iTunes with MacRuby
- Intridea - Company Blog: Build A Mac Application From Scratch Using MacRuby and Hotcocoa
- Global Nerdy: Objective-C's New NSNumber, NSArray and NSDictionary Syntaxes Mean Less Yak Shaving for iOS and OS X Developers
- Blog on Applicake's ideas, Ruby on Rails and Internet start-ups: Hope to see you soon, Jarek!