Dependency Container Unit Spec should return the corresponding value when the identifier matches a single identifier and metadata is not provided
  ✅ Dependency Container Unit Spec should return the corresponding value when the identifier matches a single identifier and metadata is not provided
Dependency Container Unit Spec should return the value of the first matching identifier when the identifier matches multiple identifiers and metadata is not provided
  ✅ Dependency Container Unit Spec should return the value of the first matching identifier when the identifier matches multiple identifiers and metadata is not provided
Dependency Container Unit Spec should return undefined when the identifier does not match any identifier
  ✅ Dependency Container Unit Spec should return undefined when the identifier does not match any identifier
Dependency Container Unit Spec should return undefined when the identifier matches a single identifier but metadata does not match
  ✅ Dependency Container Unit Spec should return undefined when the identifier matches a single identifier but metadata does not match
Dependency Container Unit Spec should return undefined when the identifier matches multiple identifiers but metadata does not match any of them
  ✅ Dependency Container Unit Spec should return undefined when the identifier matches multiple identifiers but metadata does not match any of them
Dependency Container Unit Spec should return the value of the identifier when there are two identifiers with the same token but different metadata
  ✅ Dependency Container Unit Spec should return the value of the identifier when there are two identifiers with the same token but different metadata
Dependency Container Unit Spec should return undefined when there are two identifiers with the same token and resolved with no metadata
  ✅ Dependency Container Unit Spec should return undefined when there are two identifiers with the same token and resolved with no metadata

Social TestBed Builder Integration Tests should instantiate UserService with all dependencies properly resolved
  ✅ Social TestBed Builder Integration Tests should instantiate UserService with all dependencies properly resolved
Social TestBed Builder Integration Tests should have log a warning message about http client cannot be exposed because it is not a direct dependency
  ✅ Social TestBed Builder Integration Tests should have log a warning message about http client cannot be exposed because it is not a direct dependency
Social TestBed Builder Integration Tests should log messages impl the overridden Logger.log method when UserService is initialized
  ✅ Social TestBed Builder Integration Tests should log messages impl the overridden Logger.log method when UserService is initialized
Social TestBed Builder Integration Tests should throw an error indicating the dependencies cannot be retrieved as they were exposed in the testbed
  ✅ Social TestBed Builder Integration Tests should throw an error indicating the dependencies cannot be retrieved as they were exposed in the testbed
Social TestBed Builder Integration Tests creating a user with UserService should call the verification service to verify the user data because it is mocked
  ✅ Social TestBed Builder Integration Tests creating a user with UserService should call the verification service to verify the user data because it is mocked
Social TestBed Builder Integration Tests creating a user with UserService should go through the repository because the database service is exposed
  ✅ Social TestBed Builder Integration Tests creating a user with UserService should go through the repository because the database service is exposed
Social TestBed Builder Integration Tests creating a user with UserService should successfully create and return the same user
  ✅ Social TestBed Builder Integration Tests creating a user with UserService should successfully create and return the same user
Social TestBed Builder Integration Tests getting a user info with UserService should not call the logger as the ApiService is mocked and not exposed
  ✅ Social TestBed Builder Integration Tests getting a user info with UserService should not call the logger as the ApiService is mocked and not exposed
Social TestBed Builder Integration Tests getting a user info with UserService should call the mocked ApiService to fetch the user data
  ✅ Social TestBed Builder Integration Tests getting a user info with UserService should call the mocked ApiService to fetch the user data
Social TestBed Builder Integration Tests getting a user info with UserService should go through UserApiService because it is exposed and return the data
  ✅ Social TestBed Builder Integration Tests getting a user info with UserService should go through UserApiService because it is exposed and return the data
Social TestBed Builder Integration Tests getting a user info with UserService should not expose the HttpClient because it is not a direct dependency
  ✅ Social TestBed Builder Integration Tests getting a user info with UserService should not expose the HttpClient because it is not a direct dependency
Social TestBed Builder Integration Tests should trigger the logger warning when the HttpClient is attempted to be mocked
  ✅ Social TestBed Builder Integration Tests should trigger the logger warning when the HttpClient is attempted to be mocked
  ✅ Social TestBed Builder Integration Tests should trigger the logger warning when the HttpClient is attempted to be mocked

Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "ArbitraryClassOne", with metadata undefined mocked from Symbol(MockFromMocker)
  ✅ Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "ArbitraryClassOne", with metadata undefined mocked from Symbol(MockFromMocker)
Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "ArbitraryClassTwo", with metadata undefined mocked from Symbol(MockedFromBuilder)
  ✅ Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "ArbitraryClassTwo", with metadata undefined mocked from Symbol(MockedFromBuilder)
Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "ArbitraryClassFive", with metadata undefined mocked from Symbol(MockFromMocker)
  ✅ Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "ArbitraryClassFive", with metadata undefined mocked from Symbol(MockFromMocker)
  ✅ Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "ArbitraryClassFive", with metadata undefined mocked from Symbol(MockFromMocker)
Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "custom string-based token with metadata", with metadata {"metadataKey": "value"} mocked from Symbol(MockFromMocker)
  ✅ Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "custom string-based token with metadata", with metadata {"metadataKey": "value"} mocked from Symbol(MockFromMocker)
Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "ArbitraryClassFour", with metadata undefined mocked from Symbol(MockedFromBuilder)
  ✅ Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "ArbitraryClassFour", with metadata undefined mocked from Symbol(MockedFromBuilder)
Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "custom string-based token with function", with metadata undefined mocked from Symbol(MockedFromBuilder)
  ✅ Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "custom string-based token with function", with metadata undefined mocked from Symbol(MockedFromBuilder)
Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "custom symbol-based token", with metadata {"key": "value"} mocked from Symbol(MockedFromBuilder)
  ✅ Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides override the dependencies from the builder, and leave the rest for the dependencies mocked should return a mock or a value for "custom symbol-based token", with metadata {"key": "value"} mocked from Symbol(MockedFromBuilder)
Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides should return an instance of the unit
  ✅ Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides should return an instance of the unit
Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides should log a warning indicating the dependency was not found when mocking missing dependency
  ✅ Solitary TestBed Builder Integration Test creating a testbed builder with some mock overrides should log a warning indicating the dependency was not found when mocking missing dependency

Unit Mocker Unit Spec given that the adapter returns container with the following dependencies and given there are some already mocked injectables from advanced in the mocks container when applying all the mocks on the target unit, including the already mocked should return container that lists all the dependencies together, mocked from the builder or from advanced
  ✅ Unit Mocker Unit Spec given that the adapter returns container with the following dependencies and given there are some already mocked injectables from advanced in the mocks container when applying all the mocks on the target unit, including the already mocked should return container that lists all the dependencies together, mocked from the builder or from advanced
Unit Mocker Unit Spec given that the adapter returns container with the following dependencies and given there are some already mocked injectables from advanced in the mocks container when applying all the mocks on the target unit, including the already mocked should return an instance of the class as the unit
  ✅ Unit Mocker Unit Spec given that the adapter returns container with the following dependencies and given there are some already mocked injectables from advanced in the mocks container when applying all the mocks on the target unit, including the already mocked should return an instance of the class as the unit
Unit Mocker Unit Spec given that the adapter returns container with the following dependencies and given there are some already mocked injectables from advanced in the mocks container when applying all the mocks on the target unit, including the already mocked should stay mocked
  ✅ Unit Mocker Unit Spec given that the adapter returns container with the following dependencies and given there are some already mocked injectables from advanced in the mocks container when applying all the mocks on the target unit, including the already mocked should stay mocked
Unit Mocker Unit Spec given that the adapter returns container with the following dependencies and given there are some already mocked injectables from advanced in the mocks container when applying all the mocks on the target unit, including the already mocked should apply the mocks to the class properties as well
  ✅ Unit Mocker Unit Spec given that the adapter returns container with the following dependencies and given there are some already mocked injectables from advanced in the mocks container when applying all the mocks on the target unit, including the already mocked should apply the mocks to the class properties as well

Unit Reference Unit Spec should throw an error indicating the dependency cannot be retrieved because it is faked
  ✅ Unit Reference Unit Spec should throw an error indicating the dependency cannot be retrieved because it is faked
Unit Reference Unit Spec should throw an error indicating the dependency cannot be retrieved because it is exposed
  ✅ Unit Reference Unit Spec should throw an error indicating the dependency cannot be retrieved because it is exposed
Unit Reference Unit Spec should return the corresponding class or value impl unique identifier with no metadata
  ✅ Unit Reference Unit Spec should return the corresponding class or value impl unique identifier with no metadata
  ✅ Unit Reference Unit Spec should return the corresponding class or value impl unique identifier with no metadata
  ✅ Unit Reference Unit Spec should return the corresponding class or value impl unique identifier with no metadata
  ✅ Unit Reference Unit Spec should return the corresponding class or value impl unique identifier with no metadata
  ✅ Unit Reference Unit Spec should return the corresponding class or value impl unique identifier with no metadata
Unit Reference Unit Spec should return the corresponding class or value impl unique identifier with metadata combined
  ✅ Unit Reference Unit Spec should return the corresponding class or value impl unique identifier with metadata combined
Unit Reference Unit Spec should throw an error indicating the dependency not found in case the identifier is missing
  ✅ Unit Reference Unit Spec should throw an error indicating the dependency not found in case the identifier is missing