Results for spec-first

TOON reference implementation in Rust (JSON <-> TOON)

Spec-first, cancel-correct, capability-secure async runtime for Rust.

Breakout/Arkanoid-style game built in Rust using the Bevy engine, with physics powered by bevy_rapier3d

Shahanshahi (Imperial Iranian) civil calendar types and conversions — spec-first, pre-1.0

A high-performance FHIRPath implementation in Rust with comprehensive spec compliance

🎬 AI agent director — multi-provider, stack-agnostic pipeline

Spec-first Rust port of beads_viewer (bv) — graph-aware triage for beads issue trackers (CLI binary: bvr)

Ouroboros spec-first protocol for Oxios

Oxios Agent OS — Agent Operating System powered by oxi-sdk

High-performance binary contracts and communication traits for the Aetheris Engine

High-performance binary contracts and communication traits for the Aetheris Engine

High-performance binary contracts and communication traits for the Aetheris Engine

RSpec formatter to measure run times of individual example groups

The beaker-hostgenerator tool will take a Beaker SUT (System Under Test) spec as its first positional argument and use that to generate a Beaker host configuration file.

Make sure API behavior is not changing by taking and storing a snapshot from an API response on a first run and check if they match on next spec runs.

The gem includes common tasks needed to deploy design first Open API spec to AWS using Lambdas and API Gateway

Provides an easy way for you to run your first acceptance spec to drive out your development process.

A Ruby gem for concise, behavior-first REST API specs backed by Rack::Test and RSpec.

Any automated testing should save you effort. Use the work you did writing your specs first to produce the skeleton of new projects or even just new features. Makes BDD discipline effortless to maintain.

The 'propel' script helps you to push your code to a remote server while following Continuous Integration (CI) best practices. Propel first checks the CI server to make sure it's passing, and then runs the local spec suite and pushes changes. If the remote server is failing, just have propel wait for it to pass while you get a coffee.

Attest allows you to define spec-like tests inline (within the same file as your actual code) which means almost non-existant overheads to putting some tests around your code. It also tries to not be too prescriptive regarding the 'right' way to test. You want to test private methods - go ahead, access unexposed instance variables - no worries, pending and disabled tests are first class citizens. Don't like the output format, use a different one or write your own. Infact you don't even have to define you tests inline if you prefer the 'traditional' way, separate directory and all. You should be allowed to test your code the way you want to, not the way someone else says you have to!

SpreePiwik ========== Adds piwik tracking with Ecommerce tracking Status ------ [](https://travis-ci.org/berkes/spree_piwik) [](https://codeclimate.com/github/berkes/spree_piwik) Installation ------------ Add spree_piwik to your Gemfile: ```ruby gem 'spree_piwik' ``` Bundle your dependencies and run the installation generator: ```shell bundle bundle exec rails g spree_piwik:install ``` Add your Piwik URL and site-id to the `config/initializers/spree_piwik.rb` For example: ```ruby Spree::Piwik::Config[:piwik_url] = "piwik.example.com" Spree::Piwik::Config[:piwik_id] = 1337 ``` Will use http(s)://piwik.example.com/ as url for your Piwik. And track stats for the site that has the id 1337 in Piwik. Screenshot ---------- . Testing ------- First bundle your dependencies, then run `rake`. `rake` will default to building the dummy app if it does not exist, then it will run specs. The dummy app can be regenerated by using `rake test_app`. ```shell bundle bundle exec rake ``` When testing your applications integration with this extension you may use it's factories. Simply add this require statement to your spec_helper: License ------- SpreePiwik is released under the [New BSD License](https://github.com/spree/spree/blob/master/license.md) similar to Spree.

Send SMS messages using the CellForce API

= dm-is-published This plugin makes it very easy to add different states to your models, like 'draft' vs 'live'. By default it also adds validations of the field value. Originally inspired by the Rails plugin +acts_as_publishable+ by &lt;b&gt;fr.ivolo.us&lt;/b&gt;. == Installation # Add GitHub to your RubyGems sources $ gem sources -a http://gems.github.com $ (sudo)? gem install kematzy-dm-is-published &lt;b&gt;NB! Depends upon the whole DataMapper suite being installed, and has ONLY been tested with DM 0.10.0 (next branch).&lt;/b&gt; == Getting Started First of all, for a better understanding of this gem, make sure you study the '&lt;tt&gt;dm-is-published/spec/integration/published_spec.rb&lt;/tt&gt;' file. ---- Require +dm-is-published+ in your app. require 'dm-core' # must be required first require 'dm-is-published' Lets say we have an Article class, and each Article can have a current state, ie: whether it's Live, Draft or an Obituary awaiting the death of someone famous (real or rumored) class Article include DataMapper::Resource property :id, Serial property :title, String ...&lt;snip&gt; is :published end Once you have your Article model we can create our Articles just as normal Article.create(:title =&gt; 'Example 1') The instance of &lt;tt&gt;Article.get(1)&lt;/tt&gt; now has the following things for free: * a &lt;tt&gt;:publish_status&lt;/tt&gt; attribute with the value &lt;tt&gt;'live'&lt;/tt&gt;. Default choices are &lt;tt&gt;[ :live, :draft, :hidden ]&lt;/tt&gt;. * &lt;tt&gt;:is_live?, :is_draft? or :is_hidden?&lt;/tt&gt; methods that returns true/false based upon the state. * &lt;tt&gt;:save_as_live&lt;/tt&gt;, &lt;tt&gt;:save_as_draft&lt;/tt&gt; or &lt;tt&gt;:save_as_hidden&lt;/tt&gt; converts the instance to the state and saves it. * &lt;tt&gt;:publishable?&lt;/tt&gt; method that returns true for models where &lt;tt&gt;is :published &lt;/tt&gt; has been declared, but &lt;b&gt;false&lt;/b&gt; for those where it has not been declared. The Article class also gets a bit of new functionality: Article.all(:draft) =&gt; finds all Articles with :publish_status = :draft Article.all(:draft, :author =&gt; @author_joe ) =&gt; finds all Articles with :publish_status = :draft and author == Joe Todo Need to write more documentation here.. == Usage Scenarios In a Blog/Publishing scenario you could use it like this: class Article ...&lt;snip&gt;... is :published :live, :draft, :hidden end Whereas in another scenario - like in a MenuItem model for a Restaurant - you could use it like this: class MenuItem ...&lt;snip&gt;... is :published :on, :off # the item is either on the menu or not end == RTFM As I said above, for a better understanding of this gem/plugin, make sure you study the '&lt;tt&gt;dm-is-published/spec/integration/published_spec.rb&lt;/tt&gt;' file. == Errors / Bugs If something is not behaving intuitively, it is a bug, and should be reported. Report it here: http://github.com/kematzy/dm-is-published/issues == Credits Copyright (c) 2009-07-11 [kematzy gmail com] Loosely based on the ActsAsPublishable plugin by [http://fr.ivolo.us/posts/acts-as-publishable] == Licence Released under the MIT license.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.