#rubyspec

[oneonezerozero]

A blog about ruby/rubyspec.

RubySpec 프로젝트가 MRI 진영의 참여 저조로 끝나면서 많은 구현체들이 참조할 수 있는 테스트 프레임워크가 사라진 셈이었는데, Ruby 진영에서 논의 끝에 RubySpec을 부활시키기로 결정. 포크 저장소인 ruby/rubyspec이 생겼다.

RubySpec에 핵심적인 기여를 하고 있었던 Rubinius 팀에서는 Ruby 팀의 RubySpec 포크를 쓰지 않겠다고 했지만, Rubinius가 아닌 다른 구현체(JRuby, Opal 등)에서는 크게 반길 일이다.

[rubypostit]

Generally, RSpec specs describe the expected behavior of code. While RSpec is fairly young, there are some conventions for writing specs. The RubySpecs cover a wide variety of components, so we have developed some pragmatic conventions to handle the various situations. As noted below, some conventions are more rigid than others.

These conventions apply to all specs. Existing specs that deviate from these conventions need to be fixed. Consistency is the principle that will almost always trump other conventions. Consistency aids understanding and readability. There are many thousands of lines of code in the spec files, so the value of consistency cannot be overstated.