RubySpec
This article may meet Wikipedia's criteria for speedy deletion as an article about a company, corporation or organization that does not credibly indicate the importance or significance of the subject. Note that educational institutions are not eligible under this criterion. See CSD A7.
If this article does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message. Note that this article may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Note to administrators: this article has content on its talk page which should be checked before deletion. Administrators: check links, talk, history (last), and logs before deletion. Consider checking Google.This page was last edited by Redlock (contribs | logs) at 03:55, 20 November 2010 (UTC) (14 years ago) |
| Stable release | 0.7.4
/ August 18, 2010 |
|---|---|
| Written in | Ruby |
| Operating system | Cross-platform |
| Type | Ruby programming language specifications tests |
| Website | www.rubyspec.org |
The RubySpec project aims to write a complete executable specification for the Ruby programming language. This project contains specs that describe Ruby language syntax and standard library classes. The project contains two main components:
- the RubySpec sources
- the MSpec framework
The RubySpec test suite captures most of 1.8.6/1.8.7/1.9 behavior as a reference conformance tool. Ruby MRI 1.9.2 currently passes over 99% of RubySpec.[1]
History
The RubySpec tests were initially created in 2006 for the Rubinius project, with significant contribution from the JRuby project[2]. It is now used in other Ruby implementation projects such as IronRuby[3].
See also
References
- ^ "Ruby 1.9.2 is released". Retrieved 2010-10-23.
- ^ "RubySpec". Retrieved 2010-10-23.
The project began as part of Rubinius (now sponsored by Engine Yard) and most of the work was done by contributors to Rubinius, with significant contribution by JRuby collaborators. Engine Yard has provided extensive financial support for this project, employing Evan Phoenix since June 2007 and several more full-time developers since January 2008. See History for more details of the project's timeline.
- ^ "RubySpec". Retrieved 2010-10-23.
The IronRuby GIT repo includes a copy of the RubySpec tests, including the MSpec test framework, under External.LCA_RESTRICTED\Languages\IronRuby\mspec. This makes it easy to modify existing tests or write new tests, and fix the bugs in the IronRuby sources, all in a single commit to the IronRuby repo.
External links
 | This software article is a stub. You can help Wikipedia by expanding it. |