Updated Assert.Fail() to use interpolated strings instead of string.F… #989
Annotations
12 errors and 81 warnings
ci (ubuntu-latest, Debug):
UnitTests/IO/ChainedStreamTests.cs#L38
The field chained should be Disposed in a method annotated with
|
ci (ubuntu-latest, Debug)
Process completed with exit code 1.
|
ci (ubuntu-latest, Debug)
Process completed with exit code 1.
|
ci (ubuntu-latest, Release)
Process completed with exit code 1.
|
ci (ubuntu-latest, Release):
UnitTests/IO/ChainedStreamTests.cs#L38
The field chained should be Disposed in a method annotated with
|
ci (ubuntu-latest, Release)
Process completed with exit code 1.
|
ci (windows-latest, Debug)
Process completed with exit code 1.
|
ci (windows-latest, Debug):
UnitTests/IO/ChainedStreamTests.cs#L38
The field chained should be Disposed in a method annotated with
|
ci (windows-latest, Debug)
Process completed with exit code 1.
|
ci (windows-latest, Release):
UnitTests/IO/ChainedStreamTests.cs#L38
The field chained should be Disposed in a method annotated with
|
ci (windows-latest, Release)
Process completed with exit code 1.
|
ci (windows-latest, Release)
Process completed with exit code 1.
|
ci (ubuntu-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Debug):
UnitTests/Utils/ValueStringBuilderTests.cs#L88
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
ci (ubuntu-latest, Debug):
UnitTests/Utils/ValueStringBuilderTests.cs#L108
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
ci (ubuntu-latest, Debug):
UnitTests/AssortedTests.cs#L62
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Debug):
UnitTests/AssortedTests.cs#L66
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Debug):
UnitTests/AssortedTests.cs#L78
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Debug):
UnitTests/AssortedTests.cs#L82
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Debug):
UnitTests/AssortedTests.cs#L44
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Debug):
UnitTests/AssortedTests.cs#L50
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Debug):
UnitTests/ArgumentExceptionTests.cs#L51
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Debug):
UnitTests/ArgumentExceptionTests.cs#L55
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L88
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
ci (ubuntu-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L108
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
ci (ubuntu-latest, Release):
UnitTests/AssortedTests.cs#L44
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Release):
UnitTests/AssortedTests.cs#L50
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L39
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L15
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L18
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L42
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L19
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L43
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (ubuntu-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (ubuntu-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Debug):
UnitTests/Utils/ValueStringBuilderTests.cs#L88
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
ci (windows-latest, Debug):
UnitTests/Utils/ValueStringBuilderTests.cs#L108
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
ci (windows-latest, Debug):
UnitTests/AssortedTests.cs#L62
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Debug):
UnitTests/AssortedTests.cs#L44
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Debug):
UnitTests/AssortedTests.cs#L66
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Debug):
UnitTests/AssortedTests.cs#L50
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Debug):
UnitTests/Utils/ValueStringBuilderTests.cs#L39
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Debug):
UnitTests/Utils/ValueStringBuilderTests.cs#L15
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Debug):
UnitTests/Utils/ValueStringBuilderTests.cs#L42
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Debug):
UnitTests/Utils/ValueStringBuilderTests.cs#L18
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Debug)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L88
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
ci (windows-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L108
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
ci (windows-latest, Release):
UnitTests/AssortedTests.cs#L62
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Release):
UnitTests/AssortedTests.cs#L66
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L39
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L42
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L43
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Release):
UnitTests/AssortedTests.cs#L78
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L56
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Release):
UnitTests/Utils/ValueStringBuilderTests.cs#L57
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, ClassicAssert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
ci (windows-latest, Release)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
MimeKit.4.3.0.989-ubuntu-latest-Debug-TestResults.xml
Expired
|
1.09 KB |
|
MimeKit.4.3.0.989-ubuntu-latest-Release-TestResults.xml
Expired
|
1.1 KB |
|
MimeKit.4.3.0.989-windows-latest-Debug-TestResults.xml
Expired
|
1.07 KB |
|
MimeKit.4.3.0.989-windows-latest-Release-TestResults.xml
Expired
|
1.08 KB |
|
MimeKit.4.3.0.989.nupkg
Expired
|
6.45 MB |
|