From 94f15aba402ebb5c0e1b382a5c83e6cb7c3ecc2a Mon Sep 17 00:00:00 2001 From: Christian Passlack Date: Mon, 23 Mar 2015 20:30:01 +0100 Subject: [PATCH] Updated Test-Cases of CPNumberFormater and CPTextfield because of the changes for fix #2332. The test-cased failed, because now a a CPDecimalNumber has a different UID compared to a CPNumber with the same value. That means isEqual: will return false. In the test-cases the formatter now generates CPNumbers to make the two Numbers compareable via isEqual. --- Tests/AppKit/CPTextFieldTest.j | 1 + Tests/Foundation/CPNumberFormatterTest.j | 1 + 2 files changed, 2 insertions(+) diff --git a/Tests/AppKit/CPTextFieldTest.j b/Tests/AppKit/CPTextFieldTest.j index bca749b45..5754fed59 100644 --- a/Tests/AppKit/CPTextFieldTest.j +++ b/Tests/AppKit/CPTextFieldTest.j @@ -29,6 +29,7 @@ [numberFormatter setNumberStyle:CPNumberFormatterDecimalStyle]; [numberFormatter setMaximumFractionDigits:3]; + [numberFormatter setGeneratesDecimalNumbers:NO]; [control setFormatter:numberFormatter]; [control setStringValue:@"12.3456"]; diff --git a/Tests/Foundation/CPNumberFormatterTest.j b/Tests/Foundation/CPNumberFormatterTest.j index 81d994824..14ca5e800 100644 --- a/Tests/Foundation/CPNumberFormatterTest.j +++ b/Tests/Foundation/CPNumberFormatterTest.j @@ -62,6 +62,7 @@ [numberFormatter setMinimum:10]; [numberFormatter setMaximum:20]; + [numberFormatter setGeneratesDecimalNumbers:NO]; [self assertTrue:[numberFormatter getObjectValue:objectValueRef forString:@"10" errorDescription:nil] message:@"MinMax T1: Expected True."];