Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VIH-9901 - new notify template for lip 3rd email 48 hour reminder #143

Merge branch 'master' into VIH-9901---New-Notify-template-for-LIP---3…

e712351
Select commit
Loading
Failed to load commit list.
Closed

VIH-9901 - new notify template for lip 3rd email 48 hour reminder #143

Merge branch 'master' into VIH-9901---New-Notify-template-for-LIP---3…
e712351
Select commit
Loading
Failed to load commit list.
Azure Pipelines / hmcts.vh-notification-api.sds.pr-release failed Oct 6, 2023 in 3m 29s

Build #202310060647-1 had test failures

Details

Tests

  • Failed: 3 (4.00%)
  • Passed: 72 (96.00%)
  • Other: 0 (0.00%)
  • Total: 75

Annotations

Check failure on line 22 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / hmcts.vh-notification-api.sds.pr-release

Build log #L22

Bash exited with code '1'.

Check failure on line 814 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / hmcts.vh-notification-api.sds.pr-release

Build log #L814

Creating network "hmctsvh-notification-api_integration-tests" with driver "bridge"

Check failure on line 815 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / hmcts.vh-notification-api.sds.pr-release

Build log #L815

Pulling test-db (mcr.microsoft.com/azure-sql-edge:)...

Check failure on line 816 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / hmcts.vh-notification-api.sds.pr-release

Build log #L816

Building vh-notification-api-tests

Check failure on line 1 in NotificationApi.IntegrationTests.Seeding.TemplateDataSeedingTests.should_remove_templates_where_id_do_not_match

See this annotation in the file changed.

@azure-pipelines azure-pipelines / hmcts.vh-notification-api.sds.pr-release

NotificationApi.IntegrationTests.Seeding.TemplateDataSeedingTests.should_remove_templates_where_id_do_not_match

Expected _dbContext.Templates.Count() to be 47, but found 41.
Raw output
   at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message)
   at FluentAssertions.Execution.TestFrameworkProvider.Throw(String message)
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
   at FluentAssertions.Execution.AssertionScope.FailWith(Func`1 failReasonFunc)
   at FluentAssertions.Numeric.NumericAssertions`1.Be(T expected, String because, Object[] becauseArgs)
   at NotificationApi.IntegrationTests.Seeding.TemplateDataSeedingTests.should_remove_templates_where_id_do_not_match() in /app/NotificationApi/NotificationApi.IntegrationTests/Seeding/TemplateDataSeedingTests.cs:line 63

Check failure on line 1 in NotificationApi.IntegrationTests.Seeding.TemplateDataSeedingTests.should_add_templates_for_an_environment

See this annotation in the file changed.

@azure-pipelines azure-pipelines / hmcts.vh-notification-api.sds.pr-release

NotificationApi.IntegrationTests.Seeding.TemplateDataSeedingTests.should_add_templates_for_an_environment

Expected _dbContext.Templates.Count() to be 47, but found 41.
Raw output
   at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message)
   at FluentAssertions.Execution.TestFrameworkProvider.Throw(String message)
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
   at FluentAssertions.Execution.AssertionScope.FailWith(Func`1 failReasonFunc)
   at FluentAssertions.Numeric.NumericAssertions`1.Be(T expected, String because, Object[] becauseArgs)
   at NotificationApi.IntegrationTests.Seeding.TemplateDataSeedingTests.should_add_templates_for_an_environment() in /app/NotificationApi/NotificationApi.IntegrationTests/Seeding/TemplateDataSeedingTests.cs:line 39

Check failure on line 1 in NotificationApi.UnitTests.Domain.NotificationTypeEnumTests.should_have_same_values_in_public_contract

See this annotation in the file changed.

@azure-pipelines azure-pipelines / hmcts.vh-notification-api.sds.pr-release

NotificationApi.UnitTests.Domain.NotificationTypeEnumTests.should_have_same_values_in_public_contract

Expected contractValues.All(v => availableValues.Contains((NotificationApi.Domain.Enums.NotificationType)v)) to be true, but found False.
Raw output
   at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message)
   at FluentAssertions.Execution.TestFrameworkProvider.Throw(String message)
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
   at FluentAssertions.Execution.AssertionScope.FailWith(Func`1 failReasonFunc)
   at FluentAssertions.Execution.AssertionScope.FailWith(Func`1 failReasonFunc)
   at FluentAssertions.Execution.AssertionScope.FailWith(String message, Object[] args)
   at FluentAssertions.Primitives.BooleanAssertions.BeTrue(String because, Object[] becauseArgs)
   at NotificationApi.UnitTests.Domain.NotificationTypeEnumTests.should_have_same_values_in_public_contract() in /app/NotificationApi/NotificationApi.UnitTests/Domain/NotificationTypeEnumTests.cs:line 23