Skip to content

v1.0.1 Elements() method optimized #5

v1.0.1 Elements() method optimized

v1.0.1 Elements() method optimized #5

Triggered via push April 2, 2024 18:30
Status Success
Total duration 37s
Artifacts

dotnet.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
build: Pythonize.Counter.Net.Tests/CounterTests.cs#L16
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, Assert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
build: Pythonize.Counter.Net.Tests/CounterTests.cs#L17
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, Assert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
build: Pythonize.Counter.Net.Tests/CounterTests.cs#L18
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, Assert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
build: Pythonize.Counter.Net.Tests/CounterTestsElements.cs#L16
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, Assert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
build: Pythonize.Counter.Net.Tests/CounterTestsElements.cs#L17
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, Assert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
build: Pythonize.Counter.Net.Tests/CounterTestsElements.cs#L18
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, Assert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
build: Pythonize.Counter.Net.Tests/CounterTestsElements.cs#L19
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, Assert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
build: Pythonize.Counter.Net.Tests/CounterTests.cs#L56
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, Assert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
build: Pythonize.Counter.Net.Tests/CounterTests.cs#L57
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, Assert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)
build: Pythonize.Counter.Net.Tests/CounterTests.cs#L58
Consider using the constraint model, Assert.That(actual, Is.EqualTo(expected)), instead of the classic model, Assert.AreEqual(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2005.md)