Matt Button BRMatt

I'm a fan of MiniTest::Spec. It strikes a nice balance between the simplicity of TestUnit and the readable syntax of RSpec. When I first switched from RSpec to MiniTest::Spec, one thing I was worried I would miss was the ability to add matchers. (A note in terminology: "matchers" in MiniTest::Spec refer to something completely different than "matchers" in RSpec. I won't get into it, but from now on, let's use the proper term: "expectations").

Understanding MiniTest::Expectations

Let's take a look in the code (I'm specifically referring to the gem, not the standard library that's built into Ruby 1.9):

# minitest/spec.rb

module MiniTest::Expectations

SSH setup for remote pairing

If Animal and Fozzie wanted to pair on Animals machine and they both have access to shared.muppets.com then they could use the following setup

Animal will have the following in ~/.ssh/config

Host tunnel_from_muppets
  Hostname shared.muppets.com
 RemoteForward 1235 localhost:22

Dear Rubyists,

I just lost a contract because of my code in a Rails project.

The specific code in question is related to a "posting a comment" feature. Here are the details:

In this project, "posting a comment" does not simply entail inserting a row into the database. It involves a procedure to yes, insert a row, but also detect its language, check for spam, send emails, and "share" it to Twitter and Facebook. I believe this algorithm should be encapsulated. I do not believe it belongs in a controller or a model. I do not believe Active Record callbacks should be used.

The "senior developer", whom is the stake holder's right hand man, said this:

DataMapper v2 Resources

Components

Mapper https://github.com/solnic/dm-mapper
Alternative Mapper https://github.com/mbj/mapper
Attributes/Models https://github.com/solnic/virtus

	def generate_secure_s3_url(s3_key)
	#
	# s3_key would be a path (including filename) to the file like: "folder/subfolder/filename.jpg"
	# but it should NOT contain the bucket name or a leading forward-slash
	#
	# this was built using these instructions:
	# http://docs.amazonwebservices.com/AmazonS3/latest/dev/index.html?S3_QSAuth.html
	# http://aws.amazon.com/code/199?_encoding=UTF8&jiveRedirect=1

	s3_base_url = MyApp::Application::S3_BASE_URL # i.e. https://mybucket.s3.amazonaws.com

	# This file defines regular expression patterns that can be used to
	# rewrite metric names in a search & replace fashion. It consists of two
	# sections, [pre] and [post]. The rules in the pre section are applied to
	# metric names as soon as they are received. The post rules are applied
	# after aggregation has taken place.
	#
	# The general form of each rule is as follows:
	#
	# regex-pattern = replacement-text
	#

	<?php

	require_once '/var/lib/jenkins/github/lib/Github/Autoloader.php';

	Github_Autoloader::register();

	$github = new Github_Client();

	$account = "kohana";
	$repos = array("kohana", "core", "auth", "cache", "codebench", "database", "image", "orm", "unittest", "userguide", "minion");

	1 "The Little Schemer - 4th Edition"
	Daniel P. Friedman; Paperback; $21.82
	In Stock
	Sold by: Amazon.com

	1 "Game Physics Engine Development, Second Edition: How to Build a Robust Commercial-Grade Physics Engine for your Game"
	Millington, Ian; Paperback; $31.61
	In Stock
	Sold by: Amazon.com

	#This is the "site config" for nginx

	upstream django {
	# Distribute requests to servers based on client IP. This keeps load
	# balancing fair but consistent per-client. In this instance we're
	# only using one uWGSI worker anyway.
	ip_hash;
	server unix:/tmp/uwsgi.sock;
	}
	server {

	function git_prompt_info() {
	ref=$(git symbolic-ref HEAD 2> /dev/null) \|\| return
	echo "$ZSH_THEME_GIT_PROMPT_PREFIX${ref#refs/heads/}$ZSH_THEME_GIT_PROMPT_SUFFIX"
	}