Merge pull request #165 from trustbit/handle-expired-token
GitHub Actions / Test Report - Contexture Backend
succeeded
Mar 19, 2024 in 0s
67 passed, 0 failed and 0 skipped
✅ backend/Contexture.Api.Tests/TestResults/TestResults.trx
67 tests were completed in 32s with 67 passed, 0 failed and 0 skipped.
✅ Contexture.Api.Tests.ApiTests+BoundedContexts
✅ Can list all bounded contexts
✅ When trying to delete a namespace with a malformed namespace-id then the bounded context is not deleted instead
✅ Contexture.Api.Tests.ApiTests+Namespaces
✅ Can create a new namespace
✅ Contexture.Api.Tests.EventStore+InMemoryEventStore
✅ canReadFromAnEmptyStore
✅ canReadFromAnStoreWithMultipleStreamsAndMultipleEvents
✅ canReadFromAnStoreWithOneStreamAndOneEvent
✅ Stream_WriteIntoEmptyEventStore_RereadWrittenEvent
✅ Subscribe_AppendToAnExistingStream_ReceiveOnlyLatestEventViaSubscription
✅ Subscribe_FromSpecificPositionOfExistingStream_ReturnsOnlyEventsAfterTheStartPosition
✅ Subscribe_FromStartOfExistingStream_ReturnsAllEvents
✅ Subscribe_WriteIntoEmptyEventStore_ReceiveEventViaSubscription
✅ Contexture.Api.Tests.EventStore+MsSqlBackedEventStore
✅ canReadFromAnEmptyStore
✅ canReadFromAnStoreWithMultipleStreamsAndMultipleEvents
✅ canReadFromAnStoreWithOneStreamAndOneEvent
✅ Stream_WriteIntoEmptyEventStore_RereadWrittenEvent
✅ Subscribe_AppendToAnExistingStream_ReceiveOnlyLatestEventViaSubscription
✅ Subscribe_FromSpecificPositionOfExistingStream_ReturnsOnlyEventsAfterTheStartPosition
✅ Subscribe_FromStartOfExistingStream_ReturnsAllEvents
✅ Subscribe_WriteIntoEmptyEventStore_ReceiveEventViaSubscription
✅ Contexture.Api.Tests.PositionStorage.InMemoryPositionStorage
✅ CanReadExistingFromStorage
✅ CanReadNoneFromEmptyStorage
✅ CanUpdateExistingEntry
✅ CanWriteIntoEmptyStorage
✅ Contexture.Api.Tests.PositionStorage.SqlServerPositionStorage
✅ CanReadExistingFromStorage
✅ CanReadNoneFromEmptyStorage
✅ CanUpdateExistingEntry
✅ CanWriteIntoEmptyStorage
✅ Contexture.Api.Tests.Security+using ApiKeyAuthentication scheme+accessing frontend routes
✅ with invalid api key return ok
✅ with valid api key return ok
✅ without api key should return ok
✅ Contexture.Api.Tests.Security+using ApiKeyAuthentication scheme+getting data
✅ with invalid api key should return unauthorized
✅ with valid api key should return ok
✅ without api key should return unauthorized
✅ Contexture.Api.Tests.Security+using ApiKeyAuthentication scheme+modifying data
✅ with invalid api key return unauthorized
✅ with valid api key should return ok
✅ without api key should return unauthorized
✅ Contexture.Api.Tests.Security+using Bearer scheme+accessing frontend routes
✅ with access token and invalid claims should return ok
✅ with access token and valid claims should return ok
✅ without access token should return ok
✅ Contexture.Api.Tests.Security+using Bearer scheme+getting data
✅ with access token and invalid claims should return ok
✅ with access token and valid claims should return ok
✅ without access token should return ok
✅ Contexture.Api.Tests.Security+using Bearer scheme+modifying data
✅ with access token and invalid claims should return forbidden
✅ with access token and valid claims should return ok
✅ without access token should return unauthorized
✅ Contexture.Api.Tests.Specs.BoundedContext.Searching
✅ Can search for bounded contexts by label and value for a specific template
✅ Contexture.Api.Tests.Specs.BoundedContext.Searching+When searching for bounded contexts
✅ When searching with a random query string a bad request is returned
✅ with a single, exact parameter then only the bounded context is found(parameterName: "BoundedContext.name", parameterValue: "bounded-context")
✅ with a single, exact parameter then only the bounded context is found(parameterName: "BoundedContext.shortName", parameterValue: "BC-1")
✅ with a single, exact parameter then only the bounded context is found(parameterName: "Domain.name", parameterValue: "domain")
✅ with a single, exact parameter then only the bounded context is found(parameterName: "Domain.shortName", parameterValue: "DO-1")
✅ with a single, exact parameter then only the bounded context is found(parameterName: "Label.name", parameterValue: "Architect")
✅ with a single, exact parameter then only the bounded context is found(parameterName: "Label.value", parameterValue: "John Doe")
✅ with a single, exact parameter then only the bounded context is found(parameterName: "Namespace.name", parameterValue: "Team")
✅ with a single, exact parameter then only the bounded context is found(parameterName: "Namespace.template", parameterValue: "A9F5D70E-B947-40B6-B7BE-4AC45CFE7F34")
✅ with one single and exact parameter and one non-matching wildcard search, then no bounded context should be found
✅ Contexture.Api.Tests.Specs.BoundedContext.Searching+When searching for bounded contexts+with a single string based parameter
✅ it is possible to find label names by using '*rchitec*' as Contains
✅ it is possible to find label names by using '*tect' as EndsWith
✅ it is possible to find label names by using 'arch*' as StartsWith
✅ it is possible to find namespace names by using '*ea*' as Contains
✅ Contexture.Api.Tests.Specs.BoundedContext.Searching+When searching for two different label names
✅ Given one bounded context with two different labels in the same namespace, then the bounded context is found
✅ Given one bounded context with two different labels in two different namespaces, then the bounded context is found
✅ Given two bounded contexts with different label names, then no bounded context should be found
✅ Contexture.Api.Tests.Specs.Deleting
✅ When deleting a domain the bounded contexts, collaborations and namespaces are deleted with it
✅ When deleting a domain with subdomains then the subdomain, bounded contexts and namespaces are deleted with it
✅ When deleting the bounded context the collaborations and namespaces are deleted with it
✅ Tests
✅ Unversioned JSON deserialization
Loading