> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/test-optimization/how-it-works/associating-code-with-tests/one-to-one-mapping.md). # One-to-One Mapping To establish a code-to-test mapping that is inherently precise right from the start, tools like OpenTelemetry can be employed. If your application is instrumented with OpenTelemetry, signifying the integration of OpenTelemetry libraries into your software (available for various programming languages), your application generates telemetry data. This data encompasses traces of every operation within your application, facilitating a comprehensive understanding of a request's journey through diverse services within a distributed system. The OpenTelemetry SDK efficiently gathers this telemetry data from your application and manages context propagation across service boundaries. This entails tracking the connections between different operations, even when they occur on distinct services or servers. *** ## Efficient Code-to-Test Mapping with OpenTelemetry Harnessing OpenTelemetry data can expedite the creation of an accurate code-to-test mapping. If your organization already utilizes OpenTelemetry, integrating it with Test Optimization requires minimal effort. However, it's crucial to ensure that all components interacting with the code support OpenTelemetry. If even a single component disrupts communication between OpenTelemetry and the application, the data becomes unusable. To guarantee seamless integration, thoroughly examine every aspect of your architecture, including event managers, message queues databases, agents, front-end agents, test runners and any other relevant element. Validate that every component can effectively exchange data with OpenTelemetry, ensuring uninterrupted communication and accurate test impact analysis. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sealights.io/knowledgebase/test-optimization/how-it-works/associating-code-with-tests/one-to-one-mapping.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.