Skip to content

C-sharp SDK Test workflow on workflow_dispatch #159

C-sharp SDK Test workflow on workflow_dispatch

C-sharp SDK Test workflow on workflow_dispatch #159

Manually triggered August 6, 2025 07:13
Status Success
Total duration 3m 57s
Artifacts

reviewing_changes.yml

on: workflow_dispatch
Matrix: comment-run
Fit to window
Zoom out
Zoom in

Annotations

32 warnings and 2 notices
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
The actual value should not be a constant - perhaps the actual value and the expected value have switched places (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2007.md)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L23
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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
The actual value should not be a constant - perhaps the actual value and the expected value have switched places (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2007.md)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L23
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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
The actual value should not be a constant - perhaps the actual value and the expected value have switched places (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2007.md)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L23
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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
The actual value should not be a constant - perhaps the actual value and the expected value have switched places (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2007.md)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L23
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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
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)
NUnit Repo 6.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
The actual value should not be a constant - perhaps the actual value and the expected value have switched places (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2007.md)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L23
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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
The actual value should not be a constant - perhaps the actual value and the expected value have switched places (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2007.md)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L23
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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
The actual value should not be a constant - perhaps the actual value and the expected value have switched places (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2007.md)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L23
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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
The actual value should not be a constant - perhaps the actual value and the expected value have switched places (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2007.md)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L23
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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.cs#L21
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)
NUnit Repo 5.0.x - windows-latest Sample: NUnit-BrowserStack/SampleTest.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)
NUnit Repo 6.0.x - windows-latest Sample
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
NUnit Repo 5.0.x - windows-latest Sample
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677