Thanks for your quick response! The difficulties that I'm having more specifically is that I've followed the instructions that you've provided and when I push to the repository, Xcode Cloud doesn't start a build automatically as I expect.

The point where it fails is the XCTAssertEqual method when it goes to do the check since a color that isn't loaded doesn't equal the expected color.

I don't understand how you are determining that there is no code in the bundle? How would I fix this in order to get the code to run correctly? As for trying using AppKit or UIKit as an intermediary, this was something that I really wanted to avoid because of the complexity of choosing the correct framework such that the tests are executable on any of Apple's platforms. However, I did try this and got a different error that was similar to the error that I'm still getting with these tests.

The other interesting thing is that my existing code works in applications that import the modules with the additional colours, even though these tests aren't working.

The other thing that I'm a little confused about is how is there not any code in the bundle? I am specifically trying to have code be generated in the test target and it appears that the code is being generated as expected, so wouldn't that be sufficient to ensure the existence of code in the bundle?

These steps that you are suggesting, do you suggest I implement those for the system under test (it appears to be working fine when used in an ordinary target, though doesn't work for the tests) or for the colours that the test target attempts to check the colours against? (ie are you referring to the expected colours or actual colours for these steps?)

The failure appears in the form of a test failure that says that the specified colour is not equal to a named colour that isn't loaded.

I'm a little confused how it thinks it has no code because it has test code in this bundle (the xcassets catalog is stored in the test target). I'm able to get this to work outside of the tests, so I think this is something specific to the tests. I just also tried to have the situation be in a separate target that the test target would depend on but that did nothing to fix this issue either.

When using the managedObjectModel merged from the module's bundle, it says that it's confused because it says that no model has defined an entity relating to a particular subclass of NSManagedObject.

If the assignment requires that you use UserDefaults, I would recommend choosing a different project idea since I tried using UserDefaults to save something bigger like this and it acted really weird and did not work until I switched to Core Data.