Downloadable content can fail even when the store page looks correct. Ownership may not map to the right package, files may be absent from the depot, the base game may be on the wrong build, or the game may unlock content for an account that does not own it. Verification after an update should cover the store, entitlement, delivery, installation, game behavior, and the negative case.
Define the changed surface
Record the base game, DLC name, platform, store region, DLC identifier, package or bundle, depot or file group, supported operating systems and languages, base-game version, test branch, release channel, and owner. Link the approved update and keep the previous live version available for comparison when the platform supports it.
List what players should receive: files, maps, characters, quests, cosmetic access, soundtrack, or another feature. State whether the files download separately or are already included in the base game and merely unlocked by ownership. Do not use a public description as the technical specification; tie each promised feature to an entitlement and an observable in-game result.
Steamworks' downloadable-content documentation explains that each DLC has its own app ID, while its files may either be included with the base game and gated by ownership or stored in a separate depot downloaded only for owners. It also says the DLC must be added to the appropriate packages and that the game must check ownership. Those relationships are the first things to compare after a packaging or store update.
Use clean positive and negative accounts
Prepare one account that owns the DLC and one that does not. Use accounts and devices approved for testing, with no borrowed credentials. On the positive account, confirm that the store and client show ownership. On the negative account, confirm the store offers acquisition and the game keeps paid content locked. A developer account that automatically owns every internal package cannot prove the ordinary customer path.
Steamworks' testing guidance notes that a DLC app ID must be present in a package the developer account owns, such as a developer-compensation package, before it can be tested. It also describes checking package contents and toggling test ownership for entitlement scenarios. Use the platform's documented test mechanism rather than editing production ownership or issuing untracked keys.
Verify delivery from a clean install
Test an update over an existing installation and a clean installation on each supported platform. Record download size, installed files, client DLC state, base-game build, and time. Launch the game from the normal client, not only a development executable. Confirm that the expected content appears, loads, saves, and can be revisited after restart.
Steamworks notes that new DLC content may download only when the player is running the newest game version. Test version mismatch deliberately: put the base game on the prior approved build in a controlled branch and confirm the product fails safely or updates as designed. Do not describe an incompatible state as a customer network problem without checking version and package mapping.
For optional or on-demand content, test install, pause, resume, cancellation, insufficient storage, uninstall, and reinstall. Verify that removing the DLC does not corrupt the base save. If saves contain DLC-specific objects, document what happens when content is unavailable and whether the game warns the player before loading.
Exercise entitlement and update edges
Test ownership while offline only if the platform and game explicitly support that state. Record whether the content was previously installed and whether the client had recently authenticated. Do not make a general offline promise from a single warm-cache test. Verify family sharing, region, language, architecture, and account switching only where the release actually supports them.
Install the update on top of a real prior version. Confirm that changed files replace the old ones, obsolete files do not remain active, and the in-game version matches the released package. Check multiplayer or shared-session compatibility if players with and without the DLC interact.
Close with customer-path evidence
Keep the test account, build, branch, package, DLC ID, device, timestamps, screenshots, logs, and observed results. Record known exclusions and the rollback decision maker. The change is verified only when an owning account receives and can use the correct content, a non-owning account remains correctly restricted, clean and update installs agree, version edges fail safely, and the live package mapping matches the tested candidate.
Sources
- Downloadable Content (DLC) — Valve Steamworks
- Testing on Steam — Valve Steamworks