Unity-Technologies / Unity-Technologies/UnityDataTools
Testing: add a small Addressable build including scenes
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 821
- Forks
- 71
- Avg merge
- 3h 13m
- Merged PRs (30d)
- 9
Description
The TestCommon folder has reference built content that is used for testing, we are still playing "catch up" because the testing coverage is still spotty for all the different build pipelines and variations that UnityDataTool covers.
Currently there is no reference AssetBundles that are built by Addressables so testing of that case has only happened in adhoc fashion, e.g. with large projects. Its primarily Analyze that is of concern - the dump, archive and serialized-file commands are generalized enough that they are unlikely to have bugs specific to Addressables.
The "Scene" case is a particular special case and required fixing because it wasn't properly handled by Analyze (issue #81). So any reference content should include at least one AssetBundle containing scenes.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the TestCommon folder by reviewing the existing reference built content and how Analyze consumes it. Build a small Addressables AssetBundle that includes at least one scene, then verify it exercises Analyze coverage for the scene case described in issue #81.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100