You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: code/Changelog.md
+98Lines changed: 98 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,101 @@
1
+
# V 3.0.0
2
+
## Major changes
3
+
* You can execute multiple check as a single batch and get every failures, instead of the first one. This can be achieved using:
4
+
* `Check.StartBatch`: stores the result of each subsequent check(s) and notifies all the errors when the returned object is disposed. Such as
5
+
`using(Check.StartBatch())
6
+
{
7
+
Check.That(sut).....
8
+
Check.That(sut)....
9
+
}`
10
+
Note that any actual exception thrown during the check phase will prevent any subsequent check from behind executed (1) and may not be reported as it may be replaced by an assertion failure exception.
11
+
This comes from C# exeption handling logic.
12
+
* You can provide anonymous types and tuples when using IsEqualTo against any type. The check will be made against all
13
+
_sut_'s propertie.
14
+
* NFluent supports Net 3.5 SP1, Net. 4.5.2 +, Net Standard 2.0+. Dropped support for Net Framework 2.0, 3.0, and 4.0, as well Net Standard<2.0.
15
+
If you can't upgrade your framework version to a supported one, please use NFluent 2.7.1.
16
+
17
+
18
+
## New Checks
19
+
*`Is`: Checks if _sut == expected_. This is a strongly typed equivalent to `IsEqualTo`.
20
+
*`IsGreaterOrEqualThan`: Checks if _sut_ >= _expected_.
21
+
*`IsLessOrEqualThan`: Checks if _sut_ <= _expected_.
22
+
23
+
## New feautres
24
+
* You can provide custom comparer for any type, using `Check.RegisterComparer` like this `Check.Register<MyType>(MyCustomComparer)`.
25
+
You can also use `RegisterLocalComparer` to limit its usage to a declaration scope.
26
+
27
+
## Breaking changes
28
+
* Equality logic changed for `IDictionary`: dictionaries are considered equals if they have the same keys and
29
+
the same values for each key. In NFluent V2, entries needed to be declared in the some order or else they were considered as **different** but **equivalent**.
30
+
* You need to specify
31
+
*`IsAnInstanceOf<nullableType>(null)` now fails (with an appropriate message). Previously, it did succeed. But,
32
+
as captured in issue #68, this behavior was triggered by a bug and kept due to a poor error message when fixed.
33
+
* The `IStructCheck<T>` interface has been removed as well as associated extensibility helper. Those were dedicated
34
+
to value `types`, you can migrate your existing extensions to the `ICheck<T>` type instead. Please open an issue if
35
+
you need help.
36
+
37
+
## Fixes
38
+
* HasFieldWithSameValues resulted in false positive when string fields had the same value.
39
+
* IsNotEqualTo now properly preserves expected type
40
+
* Improved rerporting of differences for enumerations and dictionaries to make them more consistent and fixed some inaccuracies.
41
+
42
+
## GitHub Issues
43
+
*#325, #327, #330, #332
44
+
45
+
### Obsolete
46
+
#### Marked as obsolet
47
+
*`ThatAsyncCode`: you can now use `ThatCode` even for async methods.
48
+
49
+
Here is the list of methods, classes and other obsolete stuff that have been removed in this version as well
50
+
as workaround advices.
51
+
* Drop support for Net 2.0 and 3.0: keep using NFluent V2.x versions if you support for these.
52
+
*`Check.ThatEnum`has been removed. You must use `Check.That` instead.
53
+
*`ILambdaCheck`: the definition was kept to prevent breaking build, but it was no longer used. If this is a
54
+
problem for you, open an issue
55
+
*`IsPositive` (available for numbers): please use `IsStrictlyPositive` instead.
56
+
*`IsNegative` (available for numbers): please use `IsStrictlyNegative` instead.
57
+
*`IsLessThan` (available for numbers): please use `IsStrictlyNegative` instead.
58
+
*`IsGreaterThan` (available for numbers): please use `IsStrictlyGreaterThan` instead.
59
+
*`IsSameReferenceThan`: please use `IsSameReferenceAs` instead.
60
+
*`HasFieldsEqualToThose`: please use `HasFieldsWithSameValues` instead.
61
+
*`HasFieldsNotEqualToThose`: please use `HasNotFieldsWithSameValues` instead.
62
+
*`IsAFaillingCheckWithMessage`: please use `IsAFailingCheckWithMessage` instead.
63
+
*`IsAFaillingCheck`: please use `IsAFailingCheck` instead.
64
+
*`Properties` (available for enumeration): please use `Extracting` instead.
65
+
*`Checker.BuildLinkWhich` (used for custom extension): please use `ExtensibilityHelper.BuildCheckLinkWhich` instead.
66
+
*`Checker.ExecuteCheckAndProvideSubItem` (used for custom extension): please 'ExtensibilityHelper' static class methods instead.
67
+
68
+
# V 2.8.0
69
+
## Breaking changes
70
+
* Removed typed overload for IsEqualTo. This may degrade autocompletion somewhat;
71
+
* Equality comparison logic has been slightly revised to take failing `Equals` result when the expected type provides a specific implementation (only success was used so far).
72
+
73
+
## New check
74
+
* Is : replaces the typed overload for IsEqualTo
75
+
76
+
## GitHub Issue
77
+
*#335
78
+
79
+
80
+
# V 2.7.2
81
+
## Fixes
82
+
* HasFieldWithSameValues resulted in false positive when string fields had the same value.
83
+
* IsZero failed for very small double (<1E-28) in previous versions.
84
+
* IsEquivalentTo was not permissive enougth for dictionaries.
85
+
86
+
## GitHub Issues
87
+
*#331, #333#
88
+
89
+
# V 2.7.1
90
+
# Fixes
91
+
* HasFieldsWithSameValues failed to properly compare when the expected value contained duplicate string.
92
+
More generally, instances where only checked once for equality; any subsequent check was assumed to be succesful.
93
+
This could lead to false positive (i.e. checks succeeded when it should have failed).
94
+
This regression was introduced by V 2.2.0 in 02/2018. Sorry about that.
95
+
96
+
# GitHub Issues
97
+
*#331
98
+
1
99
## V 2.7.1
2
100
### Fixes
3
101
* HasFieldsWithSameValues failed to properly compare when the expected value contained duplicate string.
Copy file name to clipboardExpand all lines: code/ReleaseNoteContentToBeInsertedWithinNuspecFile.md
+6-30Lines changed: 6 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,9 @@
1
+
#V 3.0.0.1
2
+
## Fix
3
+
* Fix `Check.ThatCode` not awaiting `Task` returning lambdas in V3.0.0. Note that `Task<T>` returning lambdas do work in V3.0.0
4
+
* an InvalidOperation is thrown when using `Check.ThatCode` on an async void method/lambda (as those cannot be awaited)
5
+
6
+
1
7
# V 3.0.0
2
8
## Major changes
3
9
* You can execute multiple check as a single batch and get every failures, instead of the first one. This can be achieved using:
@@ -65,33 +71,3 @@ problem for you, open an issue
65
71
*`Checker.BuildLinkWhich` (used for custom extension): please use `ExtensibilityHelper.BuildCheckLinkWhich` instead.
66
72
*`Checker.ExecuteCheckAndProvideSubItem` (used for custom extension): please 'ExtensibilityHelper' static class methods instead.
67
73
68
-
# V 2.8.0
69
-
## Breaking changes
70
-
* Removed typed overload for IsEqualTo. This may degrade autocompletion somewhat;
71
-
* Equality comparison logic has been slightly revised to take failing `Equals` result when the expected type provides a specific implementation (only success was used so far).
72
-
73
-
## New check
74
-
* Is : replaces the typed overload for IsEqualTo
75
-
76
-
## GitHub Issue
77
-
*#335
78
-
79
-
80
-
# V 2.7.2
81
-
## Fixes
82
-
* HasFieldWithSameValues resulted in false positive when string fields had the same value.
83
-
* IsZero failed for very small double (<1E-28) in previous versions.
84
-
* IsEquivalentTo was not permissive enougth for dictionaries.
85
-
86
-
## GitHub Issues
87
-
*#331, #333#
88
-
89
-
# V 2.7.1
90
-
# Fixes
91
-
* HasFieldsWithSameValues failed to properly compare when the expected value contained duplicate string.
92
-
More generally, instances where only checked once for equality; any subsequent check was assumed to be succesful.
93
-
This could lead to false positive (i.e. checks succeeded when it should have failed).
94
-
This regression was introduced by V 2.2.0 in 02/2018. Sorry about that.
0 commit comments