From 98a4187ad00a8db7f441ccba96dc1d78ee829875 Mon Sep 17 00:00:00 2001 From: Sri <61034258+srilovesflutter@users.noreply.github.com> Date: Fri, 11 Jul 2025 09:19:37 +0530 Subject: [PATCH] corrected typo (#129) Co-authored-by: srilovesflutter --- extensions/copilot/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/extensions/copilot/CONTRIBUTING.md b/extensions/copilot/CONTRIBUTING.md index cf7aa9b3fbc..4e492b33a71 100644 --- a/extensions/copilot/CONTRIBUTING.md +++ b/extensions/copilot/CONTRIBUTING.md @@ -95,7 +95,7 @@ There are also integration tests that run within VS Code itself: npm run test:extension ``` -Finally, there are **simulation tests**. These tests reach out to Copilot API endpoints, invoke LLMs and require expensive computations to run. Each test runs 10 times, to accomodate for the stochastic nature of LLMs themselves. The results of all runs of all tests are snapshotted in the baseline file, [`test/simulation/baseline.json`](test/simulation/baseline.json), which encodes the quality of the test suite at any given point in time. +Finally, there are **simulation tests**. These tests reach out to Copilot API endpoints, invoke LLMs and require expensive computations to run. Each test runs 10 times, to accommodate for the stochastic nature of LLMs themselves. The results of all runs of all tests are snapshotted in the baseline file, [`test/simulation/baseline.json`](test/simulation/baseline.json), which encodes the quality of the test suite at any given point in time. Because LLM results are both random and costly, they are cached within the repo in `test/simulation/cache`. This means rerunning the simulation tests and benefiting from the cache will make the test run be both faster as well as deterministic.