What process is missing if developers release code for testing that is not version controlled?

The process that is missing when developers release code for testing that is not version controlled is configuration management.

Configuration management involves systematic handling of changes to a system, including the management of files, tools, and data throughout the software development lifecycle. It ensures that the correct versions of software and related documents are available, which is crucial for a successful testing phase. Without version control, there is a high risk of confusion and errors, as testers may work with outdated or incorrect code versions, leading to inaccurate testing results.

In the context of development and testing, effective configuration management enables better collaboration, traceability of changes, and consistency across different environments. It allows teams to understand what changes have been made, by whom, and why, thereby aligning development efforts with overall project objectives and requirements. This foundational aspect is essential for maintaining the integrity and quality of the software being tested.