Skip to content
Build

Create build-only.yml #1

Sign in to view logs

Create build-only.yml

Create build-only.yml #1

Triggered via push April 2, 2024 02:54
@LukeukeLukeuke
pushed fb3b834
main
Status Success
Total duration 30s
Artifacts –

build-only.yml

on: push
build
22s
build
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
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/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/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/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/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#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/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)