Add Columns to Pending Report #188
tom-karaschdotnet-test.yml
on: pull_request
Run unit tests
2m 31s
Annotations
7 errors and 10 warnings
|
Run unit tests:
tests/FMS.App.Tests/Helpers/GeoCoordHelperTests.cs#L46
'GeoCoordHelper' does not contain a definition for 'BothZeroOrBothNonzero'
|
|
Run unit tests:
tests/FMS.App.Tests/Helpers/GeoCoordHelperTests.cs#L52
'GeoCoordHelper' does not contain a definition for 'BothZeroOrBothNonzero'
|
|
Run unit tests:
tests/FMS.App.Tests/Helpers/GeoCoordHelperTests.cs#L60
'GeoCoordHelper' does not contain a definition for 'BothZeroOrBothNonzero'
|
|
Run unit tests:
tests/FMS.App.Tests/Helpers/GeoCoordHelperTests.cs#L46
'GeoCoordHelper' does not contain a definition for 'BothZeroOrBothNonzero'
|
|
Run unit tests:
tests/FMS.App.Tests/Helpers/GeoCoordHelperTests.cs#L52
'GeoCoordHelper' does not contain a definition for 'BothZeroOrBothNonzero'
|
|
Run unit tests:
tests/FMS.App.Tests/Helpers/GeoCoordHelperTests.cs#L60
'GeoCoordHelper' does not contain a definition for 'BothZeroOrBothNonzero'
|
|
Run unit tests
Process completed with exit code 1.
|
|
Run unit tests:
FMS.Infrastructure/Migrations/20240305210424_UpdateSPnearbyFacilities2.cs#L17
Add a nested comment explaining why this method is empty, throw a 'NotSupportedException' or complete the implementation. (https://rules.sonarsource.com/csharp/RSPEC-1186)
|
|
Run unit tests:
FMS.Infrastructure/Migrations/20240223163127_UpdateSPgetNearbyFacilities.cs#L46
Use 'Guid.NewGuid()' or 'Guid.Empty' or add arguments to this GUID instantiation. (https://rules.sonarsource.com/csharp/RSPEC-4581)
|
|
Run unit tests:
tests/FMS.Infrastructure.Tests/CabinetRepositoryTest.cs#L190
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
Run unit tests:
tests/FMS.Infrastructure.Tests/CabinetRepositoryTest.cs#L209
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
Run unit tests:
tests/FMS.Infrastructure.Tests/CabinetRepositoryTest.cs#L230
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
Run unit tests:
tests/FMS.Infrastructure.Tests/CabinetRepositoryTest.cs#L249
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
Run unit tests:
tests/FMS.Infrastructure.Tests/CabinetRepositoryTest.cs#L340
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
Run unit tests:
tests/FMS.Infrastructure.Tests/CabinetRepositoryTest.cs#L360
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
Run unit tests:
tests/FMS.Infrastructure.Tests/CabinetRepositoryTest.cs#L381
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|
|
Run unit tests:
tests/FMS.Infrastructure.Tests/CabinetRepositoryTest.cs#L420
Test methods should not call ConfigureAwait(false), as it may bypass parallelization limits. Omit ConfigureAwait, or use ConfigureAwait(true) to avoid CA2007. (https://xunit.net/xunit.analyzers/rules/xUnit1030)
|