This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:safeav:ctrl:testing [2026/06/03 00:17] – [Test Tracks and Physical Testing] momala | en:safeav:ctrl:testing [2026/06/03 00:23] (current) – [Test Methods] momala | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| The central idea is that the scenario from the previous subsection must be brought into a test environment that is suitable for the question being asked. A lane-change scenario, for example, may first be explored in CARLA or another simulator, then repeated with software-in-the-loop or hardware-in-the-loop components, then confirmed at a controlled proving ground such as ZalaZONE, and finally monitored in limited real-world operation. In each case, the test method changes, but the underlying scenario remains the same. That is what makes the validation evidence comparable. | The central idea is that the scenario from the previous subsection must be brought into a test environment that is suitable for the question being asked. A lane-change scenario, for example, may first be explored in CARLA or another simulator, then repeated with software-in-the-loop or hardware-in-the-loop components, then confirmed at a controlled proving ground such as ZalaZONE, and finally monitored in limited real-world operation. In each case, the test method changes, but the underlying scenario remains the same. That is what makes the validation evidence comparable. | ||
| - | <!-- Figure comment: testing | + | {{ :en: |
| ===== Simulation-Based Testing ===== | ===== Simulation-Based Testing ===== | ||