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
Changes to handling test passing and exceptions (#83)
* Pass the test immediately if all test blocks pass and expose TestBlockException get and FinallyBlockExceptions
* Only expose readonly finally exceptions
Copy file name to clipboardExpand all lines: IntelliTect.TestTools.TestFramework/TestCase.cs
+33-22Lines changed: 33 additions & 22 deletions
Original file line number
Diff line number
Diff line change
@@ -37,22 +37,37 @@ public TestCase(string testCaseName, string testMethodName, int testCaseId, ISer
37
37
/// If a finally block fails and this property is true, the test case is still considered passed internally, but most unit test frameworks will mark the test failed.
/// If any test block throws an exception, it will be stored here. Finally block exceptions are stored separately in FinallyBlockExceptions. If this is not null at the end of the test case execution, the test case is considered failed.
/// Did the test case pass? This is determined by whether any test block threw an exception.
54
+
/// </summary>
55
+
/// <remarks>
56
+
/// Finally block exceptions do not cause the test case to be marked as failed, but they are still captured and can cause the test case to throw after execution if ThrowOnFinallyBlockException is true.
57
+
/// </remarks>
58
+
publicboolPassed{get;set;}
40
59
41
60
// May make sense to make some of the below public if it's needed for debugging.
42
61
// If so, definitely need to change them to internal or private sets.
0 commit comments