From 856ef24897a4a5c18999f8231b2379b416242760 Mon Sep 17 00:00:00 2001 From: Tim Blair Date: Wed, 8 Jul 2015 22:28:35 +0100 Subject: Use explicit values in RemoteSpecification tests The original cases ("not zero") would still pass if the check resulted in a nil response. --- spec/bundler/remote_specification_spec.rb | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/spec/bundler/remote_specification_spec.rb b/spec/bundler/remote_specification_spec.rb index fa3534d8a2..ce1e4e0358 100644 --- a/spec/bundler/remote_specification_spec.rb +++ b/spec/bundler/remote_specification_spec.rb @@ -27,8 +27,8 @@ describe Bundler::RemoteSpecification do context "which is different by name" do let(:other_name) { "a" } - it "doesn't return 0" do - expect(subject <=> other).not_to eq(0) + it "returns 1" do + expect(subject <=> other).to eq(1) end end @@ -48,8 +48,8 @@ describe Bundler::RemoteSpecification do context "which has a different platform" do let(:other_platform) { Gem::Platform.new("x86-mswin32") } - it "doesn't return 0" do - expect(subject <=> other).not_to eq(0) + it "returns -1" do + expect(subject <=> other).to eq(-1) end end end -- cgit v1.2.1