Projects tagged ‘rspec’

Cross platform BDD tool that lets domain experts define software behaviour in plain text. The text can be executed as automated tests.

Lightweight, fast and modular MVC Ruby web framework. Excellent for high performance dynamic pages and web services.

The Metasploit Framework is a development platform for creating security tools and exploits. The framework is used by network security professionals to perform penetration tests, system administrators ... [More] to verify patch installations, product vendors to perform regression testing, and security researchers world-wide. The framework is written in the Ruby programming language and includes components written in C and assembler. [Less]

Ronin is a Ruby platform for exploit development and security research. Ronin allows for the rapid development and distribution of code, exploits or payloads over many common Source-Code-Management (SCM) systems.

Spidr is a versatile Ruby web spidering library that can spider a site, multiple domains, certain links or infinitely. Spidr is designed to be fast and easy to use.

Raingrams is a flexible and general-purpose ngrams library written in Ruby. Raingrams supports ngram sizes greater than 1, text/non-text grams, multiple parsing styles and open/closed vocabulary models.

Primary Goal Have a bit of help with spec/context style BDD over the typical NUnit class=spec method=rule approach. Why Am I Building This ? I need to be able to provide well formatted reports ... [More] to business experts at my job. Why don't I use or contribute to BDD framework X ? I thought about it a lot, but fundamentally all the .Net ones I've seen either are A) acceptance given/when/then or they B) have in my opinion steeper learning curve than I'm comfortable throwing at junior devs. I wanted something that was more opinionated in its usage. [Less]

When you testing or specing a Rails app and trying to avoid database hits, the process of creating a mock model objects with all the required columns and values stubbed can be tedious. If you have ... [More] gone to the trouble of creating fixture files for you model specs then these can be reused for the controller, (functional tests), view and helper specs without the performance hit of the accessing the database. This is where mocked_fixtures comes in. For example in a spec where you have fixtures :peopleyou can replace with mock_fixtures :peopleand use the mocked models loaded with the fixture values like this @joe = mock_people(:joe)presuming you have a fixture labelled 'joe'. You get backed a mock object with all attribute methods stubbed out with the values that were in the fixture. [Less]

RStack uses rspec instead of test/unit and integrates with CruiseControl.rb. This is really, really basic. More features will be added as required. Usagerstack fooGenerated Rakefilerequire ... [More] 'rubygems' require 'rstack' require File.join(File.dirname(__FILE__), 'lib', 'foo', 'version') RStack::Configuration.new do |config| config.name = 'foo' config.summary = '[ENTER A SUMMARY]' config.author = 'jeremy burks' config.email = '[ENTER YOUR EMAIL]' config.url = '[ENTER A PROJECT URL]' config.version = Foo::Version::STRING endRStack::Configuration Defaultsconfig.name = '[ENTER A NAME]' config.summary = '[ENTER A SUMMARY]' config.author = '[ENTER A AUTHOR]' config.email = '[ENTER YOUR EMAIL]' config.url = '[ENTER A PROJECT URL]' config.version = '0.1.0' config.platform = Gem::Platform::RUBY config.spec_globs = FileList['spec/**/*_spec.rb'] config.package_globs = FileList['[a-zA-Z]*', 'bin/**/*', 'lib/**/*', 'spec/**/*'] config.require_path = 'lib' config.has_rdoc = false config.out_path = ENV["CC_BUILD_ARTIFACTS"] || 'out' config.executables = [] config.extra_dependencies = [] [Less]

a customized version of rails scaffold resource geared for use with rspec