A low-drama portfolio generator for your middleman site.

Choose emoji provider and convert emoji shorthand to <img> tag using somemoji gem.

Use version control to determine last-modified times of Middleman resources.

API client for Midea AC systems

Will import a CSV as an array of hashes. Or will export a CSV from an array of hashes (if given a column list).

ruby service container

Monkey patch for AWS ruby SDK HashModel to support model backed by DynamoDB tables with hash-range keys. It also provides some convenience methods to define your model in a more expressive rails style.

minifilter is yet another minitest output formatter and colorizer

Allows you to provide an exclusion list of allowed failures/errors. Failures and errors on this list still get run and reported as usual, but do not cause a non-zero exit code. This enables you to have a green CI with against a list of known bad tests.

A collection of assertions for use with minitest and activerecord. Simplifies testing associations and validations by introspecting associations and validations for you models.

minitest-bacon extends minitest with bacon-like functionality. It should allow you to bridge 90+% of your bacon specs over to minitest.

Bonus assertions for [Minitest][minitest], providing assertions I (used to) use frequently, supporting only Ruby 2.0 or better. > I have not used these regularly for tests in about ten years. They're still > likely good, but I no longer consider them necessary. ==== To Install:

This is a quick and dirty tool to compare test time deltas between two runs by comparing verbose run output.

Ruby's contemporary test coverage tools all lie, exaggerating coverage through false-positives and creating a false sense of security; minitest-coverage tries to address this. Coverage Analysis Tools rely on tracing facilities built into ruby’s VM. You run your tests, and collect data. Seems simple, but that’s a very flawed approach that buffers your coverage numbers up falsely. I’ve witnessed false coverage by as much as 60%, but it could be even worse. Worse, the tracing facilities currently make it impossible to get truly accurate numbers. Even so, they can be improved to be much more accurate.

This is a stupid simple example of how easy it is to make a minitest plugin that does something useful. In this case it wraps assert so that failed assertions will drop into the ruby debugger.

Additional assertions for seattlerb's popular MiniTest framework. Mostly aimed around improving compatibility with test-unit.

Print out glitch for your test passes, fails, and skips Inspired by https://github.com/tenderlove/minitest-emoji

Growl Notifications for MiniTest v5+

All pride, all the time!

minitest-macruby provides extensions to minitest for macruby UI testing. It provides a framework to test GUI apps in a live instance. Documentation and examples are light at the moment as I've just thrown this together. Suggestions for extensions are very welcome! Currently it provides the following methods in minitest's assertions: * self.run_macruby_tests * find_ui_menu(*path) * find_ui_menu_items menu * assert_ui_menu menu, *items * find_ui_menu_item(*path) * assert_ui_action obj, target, action, key = nil * assert_ui_binding item, binding_name, target, path