Skip to content

Merge remote-tracking branch 'origin/main' #10

Merge remote-tracking branch 'origin/main'

Merge remote-tracking branch 'origin/main' #10

Triggered via push April 3, 2024 22:24
Status Success
Total duration 32s
Artifacts

build-only.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/CounterTestsMostCommon.cs#L15
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/CounterTestsMostCommon.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#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/CounterTestsTotal.cs#L15
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)