GithubHelp home page GithubHelp logo

cutest's People

Contributors

bemurphy avatar britishtea avatar djanowski avatar esbanarango avatar frodsan avatar gtramontina avatar moonglum avatar patriciomacadden avatar pootsbook avatar soveran avatar tonchis avatar xymbol avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

cutest's Issues

`bad value for range`

The pivot index in the backtrace cannot be determined because the argument to #run_file executes load <other file>, which then raises an error.

bad value for range
/home/pieter/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/cutest-1.1.3/lib/cutest.rb:58:in `rescue in run_file'
/home/pieter/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/cutest-1.1.3/lib/cutest.rb:44:in `run_file'

Bail on first error

Currently cutest exits when the first error occur. Would you be interested in adding a flag -b to make that optional? The reason is that sometimes it is useful to get all errors at once.

no longer works in non-fork() environments

cutest used to have support for non-fork environments, but seems that support is gone.

Because of that, tests of cuba can't be run

Would be too complex bring non-fork() friendly cutest again?

Thank you

/cc @soveran

test failure with uninitialized constant Cutest::FILTER (NameError) with ruby 1.8

/usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
Running tests for ruby1.8 using debian/ruby-tests.rb...
...............
test: output of failed run
./debian/ruby-cutest//usr/lib/ruby/vendor_ruby/cutest.rb:36:in run_file': uninitialized constant Cutest::FILTER (NameError) from ./debian/ruby-cutest//usr/lib/ruby/vendor_ruby/cutest.rb:36:inselect'
from ./debian/ruby-cutest//usr/lib/ruby/vendor_ruby/cutest.rb:36:in run_file' from ./debian/ruby-cutest//usr/lib/ruby/vendor_ruby/cutest.rb:21:infork'
from ./debian/ruby-cutest//usr/lib/ruby/vendor_ruby/cutest.rb:21:in run_file' from ./debian/ruby-cutest//usr/lib/ruby/vendor_ruby/cutest.rb:10:inrun'
from ./debian/ruby-cutest//usr/lib/ruby/vendor_ruby/cutest.rb:9:in each' from ./debian/ruby-cutest//usr/lib/ruby/vendor_ruby/cutest.rb:9:inrun'
from debian/ruby-tests.rb:4

fixtures directory is missing from gem

tests are failing because fixtures directory is not present in gem. When trying to download directly from github 1.1.2 tag is missing. Can you upload a new gem file with fixtures directory? or at least tag 1.1.2 release here? I need it for building a debian package for cutest.

test failed with ruby1.9

Running tests for ruby1.9.1 using debian/ruby-tests.rb...
...............
test: output of failed run
line: assert_equal(expected, out)
file: /media/forge/debian/diaspora/ruby-cutest-1.2.0/test/run.rb +18

Cutest::AssertionFailed: "\n test: failed assertion\n line: assert false\n file: test/fixtures/failure.rb +2\n\nCutest::AssertionFailed: expression returned false\n\n" != "\n test: failed assertion\n line: assert false\n file: /media/forge/debian/diaspora/ruby-cutest-1.2.0/test/fixtures/failure.rb +2\n\nCutest::AssertionFailed: expression returned false\n\n"

and content of debian/ruby-tests.rb is

ENV['PATH'] = 'debian/ruby-cutest/usr/bin:' + ENV['PATH']

require "cutest"
Cutest.run(Dir["test/*.rb"])

Setup and scopes

Is this the intended behavior?

scope do
  setup do
    5
  end

  test do |i|
    assert_equal i, 5
  end
end

scope do
  test do |i|
    assert_equal i,5 ##Wooah, I thought i was supposed to be nil, given that this test belongs to a different scope...
  end
end

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.