Addressables in Editor Unit Tests

My project has added a few generated unit tests to validate that the indirect references we had in place, soon to be AssetReferences with Addressables, were pointing to valid assets or scenes. For example, we generated a new test case to make sure each of our characters had a portrait sprite attached to the metadata ScriptableObject. In this we, used the previous Asset Bundle Simulation to simulate loading from an asset bundle, synchronously loaded it, and validated that it the requirements we had set for it (not being null, being of the right size, etc.) This has been a nice safeguard against potentially having game-breaking asset load failures down the line: any run of our test suite added data validation. Is this supported in Addressaables?

 

It seems that the unity Test system doesn't really handle async tests very well, and I'm having problems using addressables in tasks (I have the exact same requirement as @james7132 ). My Completed events never fire, and calls to LoadResourceLocationsAsync return an already completed AsyncOperationHandle with no Results for addresses that work correctly at runtime. Were you able to get this working, James?

 

I was able to get the Addressables API working correctly for PlayMode tests, which is good enough for me.

 

How did you get Addressables working in PlayMode tests? I can't get past error CS0234: The type or namespace name 'AddressableAssets' does not exist in the namespace 'UnityEngine' (are you missing an assembly reference?)

 

As it says, you probably are missing an assembly reference. Ensure the assembly definition that contains your tests references Unity.Addressables and Unity.ResourceManager.

 

Hi there. I got the same problem except my test assembly has references to Unity.Addressables and unity.ResourceManager.

I have two simple tests as following:

Code (CSharp):

1.         [Test]
2.         public void CharacterCardsSystem_loadAddressables_CorrectLabel()
3.         {
4.             var handle = Addressables.LoadAssetsAsync<CharacterAbilitiesDefinitionAsset>("characterCards", null);
5.             handle.Completed += operationHandle =>
6.             {
7.                 Assert.AreEqual(handle.Status, AsyncOperationStatus.Succeeded);
8.                 foreach (var card in operationHandle.Result)
9.                 {
10.                     Assert.IsNotNull(card);
11.                 }
12.             };
13.         }

and

Code (CSharp):

1. [Test]
2.         public void CharacterCardsSystem_loadAddressables_WrongLabel()
3.         {
4.             var handle = Addressables.LoadAssetsAsync<CharacterAbilitiesDefinitionAsset>("some wrong identifier", null);
5.             handle.Completed += operationHandle =>
6.             {
7.                 Assert.IsTrue(handle.Status == AsyncOperationStatus.Failed);
8.             };
9.         }

and both tests pass. So far so good. But no matter what I put as the asset label when calling LoadAssetsAsync, both tests still pass, for example if I put a non-existing label inside the first test, it still passes. What I'm doing wrong??

I figured it might be because of callbacks. So I did a UnityTest with:

Code (CSharp):

1.   [UnityTest]
2.         public IEnumerator CharacterCardsSystem_loadAssetsAsync()
3.         {
4.             var handle = Addressables.LoadAssetsAsync<CharacterAbilitiesDefinitionAsset>("characaterCards", null);
5.             yield return handle;
6.             Assert.AreEqual(handle.Status, AsyncOperationStatus.Succeeded);
7.         }

but no matter from where I run the test (from TestRunner window in Unity or from Rider), the test gets stuck forever, not concluding with neither a fail nor a pass. The following window remains until I close it, and at that point, it fails because "test was canceled by user":

 

It would be great if assets in custom UPM packages could be marked as Addressables. The inspector doesn't show the addressables field and so all testing assets need to be placed under the Assets/ folder.