Skip to content
PR unit test

Feature/add action unit test #16

Sign in to view logs

Feature/add action unit test

Feature/add action unit test #16

Triggered via pull request August 30, 2024 07:31
@jcreachjcreach
synchronize #2
feature/add-action-unit-test
Status Failure
Total duration 22s
Billable time 1m
Artifacts –

unitTest.yml

on: pull_request
test
13s
test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 10 warnings
test
Process completed with exit code 1.
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test
Unexpected input(s) 'fail-on-error', valid inputs are ['name', 'path', 'if-no-files-found', 'retention-days']
test
No files were found with the provided path: **/*.trx. No artifacts will be uploaded.
test: katas/katas.sample.test/ArrayKataTests.cs#L9
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)
test: katas/katas.sample.test/ArrayKataTests.cs#L11
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)
test: katas/katas.sample.test/ArrayKataTests.cs#L13
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)
test: katas/katas.sample.test/ArrayKataTests.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)
test: katas/katas.sample.test/ArrayKataTests.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)
test: katas/katas.sample.test/ArrayKataTests.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)
test: katas/katas.sample.test/ArrayKataTests.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)