methods for easier css color #971
NielsPilgaardAnnotations
10 errors
|
Jordnaer.Tests.Chat.ChatNotificationServiceTests.CreateEmails_ShouldGenerateCorrectEmailContent
System.ArgumentException : Constructor arguments cannot be passed for interface mocks.
|
|
Jordnaer.Tests.Chat.ChatNotificationServiceTests.GetChatLink_ShouldReturnCorrectLink
System.ArgumentException : Constructor arguments cannot be passed for interface mocks.
|
|
Jordnaer.Tests.Chat.ChatNotificationServiceTests.CreateEmails_ShouldThrow_WhenNoRecipients
System.ArgumentException : Constructor arguments cannot be passed for interface mocks.
|
|
Jordnaer.Tests.Chat.ChatNotificationServiceTests.NotifyRecipients_ShouldFetchRecipientsAndPublishEmails
System.ArgumentException : Constructor arguments cannot be passed for interface mocks.
|
|
Jordnaer.Tests.Chat.ChatNotificationServiceTests.NotifyRecipients_ShouldNotPublishEmails_WhenNoRecipients
System.ArgumentException : Constructor arguments cannot be passed for interface mocks.
|
|
Jordnaer.Tests.Chat.ChatNotificationServiceTests.GetChatLink_ShouldReturnDefault_WhenServerAddressNotAvailable
System.ArgumentException : Constructor arguments cannot be passed for interface mocks.
|
|
Jordnaer.Tests.UserSearch.UserSearchServiceTests.Return_UserSearchResult_With_Category_Filter
System.ObjectDisposedException : Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'JordnaerDbContext'.
|
|
Jordnaer.Tests.UserSearch.UserSearchServiceTests.Return_UserSearchResult_With_CombinedName_Filter
System.ObjectDisposedException : Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'JordnaerDbContext'.
|
|
Jordnaer.Tests.UserSearch.UserSearchServiceTests.Return_UserSearchResult_With_MaximumChildAge_Filter
System.ObjectDisposedException : Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'JordnaerDbContext'.
|
|
Jordnaer.Tests.UserSearch.UserSearchServiceTests.Return_UserSearchResult_With_LastName_Filter
System.ObjectDisposedException : Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'JordnaerDbContext'.
|