Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Ruby
[ANN] testy.rb - ruby testing that's mad at the world
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="ara.t.howard, post: 4635220"] it's a valid complaint. but compare it to what you'll get in most frameworks and consider that, by beautiful, i mean that a YAML.load can slurp the entire set of expect vs actual. i considered a delta style format: diff a: expect: 42 actual: 42.0 b: expect: 43 actual: 43.0 but it seems very hard to reconstruct for downstream filters. i'm open to suggestion on format though. requirements are . readable by humans . easily parsed by computers basically that means some yaml format. honestly open to suggestion here... i personally don't think so, i think the community took a wrong turn, from wikipedia ([URL]http://en.wikipedia.org/wiki/[/URL] Behavior_Driven_Development) " The practices of BDD include: * Involving stakeholders in the process through outside-in software development * Using examples to describe the behavior of the application, or of units of code * Automating those examples to provide quick feedback and regression testing * In software tests, using 'should' to help clarify responsibility and allow the software's functionality to be questioned * Test use 'ensure' to differentiate outcomes in the scope of the code in question from side-effects of other elements of code. * Using mocks to stand-in for modules of code which have not yet been written i have major issues with points two and three wrst to most ruby testing frameworks. one of the main points of testy is to combine examples with testing. rspec and all the others do not serve as examples unless you are a ruby master. that is to say they introduce too many additions to the code that's supposed to be an example to really preserve it's 'exampleness'. and of course the output is utterly useless to normal humans. if a framework provides 1000 asset_xxxxxxxx methods ad nausea then the point of the code - it's level of example-good-ness - is lost to mere mortals this will summarize where my thoughts are on that cfp:~/redfission > find vendor/gems/{faker,mocha,thoughtbot}* -type f| xargs -n1 cat|wc -l 24255 cfp:~/redfission > find app -type f|xargs -n1 cat|wc -l 1828 rspec and co might be fine but seriously, the above is insane right? kind regards. a @ [URL]http://codeforpeople.com/[/URL] [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Ruby
[ANN] testy.rb - ruby testing that's mad at the world
Top