wrong

wrong copied to clipboard

Need to update MiniTest adapter.

4

I've tried `wrong` with the latest minitest version 5.0.6 and it failed. 1) Error: UnitTest#test_assert_true: NoMethodError: undefined method `_assertions' for # /Users/ava/git/wrong/lib/wrong/adapters/minitest.rb:13:in`aver' /Users/ava/git/wrong/lib/wrong/assert.rb:34:in `assert' unit_test.rb:6:in`test_assert_true' Since the latest version MiniTest...

av-ast

``` require 'wrong' include Wrong assert{(1..2) == (1..1)} ``` produces a NoMethodError instead of the usual description (tested on ruby 2.1 and 1.9.3)

eqv

RubyGems.org doesn't report a license for your gem. This is because it is not specified in the [gemspec](http://docs.rubygems.org/read/chapter/20#license) of your last release. via e.g. ``` spec.license = 'MIT' # or...

bf4

conflicts with minitest in Rails 4 and rspec_rails

6

In Rails 4 with rspec_rails, my `assert` method is from minitest, not from wrong. Here's an app demonstrating the problem: https://github.com/jjb/rails_4_rspec_rails_wrong Here's the relevant commit: https://github.com/jjb/rails_4_rspec_rails_wrong/commit/c59d8f45388dd267f291151d51445770188a7a5a I tried putting `require...

jjb

Project name feels wrong - can't google it :(

4

Hi Steve, Having written assert_\* and should bla for 12 years, I was quite curious about the "Wrong" way. So far, so good:) Googling "wrong" related articles is difficult, would...

jmgarnier

https://github.com/ranmrdrakono/wrong/blob/master/lib/wrong/assert.rb#L23-L24 This lines cause race conditions. I propose to use thread_variable to identify recursion problems while avoiding multi threading issues

eqv

NameError on otherwise un-referenced block arg in failing example

1

Given the following failing example in failing_example.rb ``` ruby require 'wrong/adapters/rspec' describe "a block arg in a failing assertion" do it "raises a NameError :(" do assert { [].each {|v|}...

dchelimsky

parse the last line of the block only on failure????

3

So I have this kinda crazy idea for integrating wrong with rspec: ``` ruby describe User do it "has the read-only role by default" do User.new.role == Role::READ_ONLY end end...

dchelimsky

wrong causes assert_select to fail

1

I am using rspec with wrong in a rails app. I have the followin in my `spec_helper.rb` file: ``` require "wrong/adapters/rspec" Wrong.config.alias_assert :confirm ``` However, when I used `assert_select`, eg:...

davidmiani

I found an odd behavior when using eventually and should_not be_nil. ``` ruby it "should work with be_nil" do found = "X" eventually { found.should_not be_nil } end ``` Error...

ziobrando