From b12d235bae8e8f6ffa83aba36420a781dcfd3a61 Mon Sep 17 00:00:00 2001 From: Jannis R Date: Thu, 7 Dec 2023 00:54:56 +0100 Subject: [PATCH] =?UTF-8?q?contributing.md:=20link=20to=20testing=20docs?= =?UTF-8?q?=20=F0=9F=93=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- contributing.md | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/contributing.md b/contributing.md index f7740fcc..1a23824d 100644 --- a/contributing.md +++ b/contributing.md @@ -4,11 +4,4 @@ Thanks for helping! 🙏 ## Adding integration/end-to-end tests -The [end-to-end/system tests](https://en.wikipedia.org/wiki/System_testing) in [`test/e2e`](test/e2e), executing via `npm run test-e2e`, are querying real HAFAS endpoints, expecting valid & *reasonable* responses. - -The [integration tests](https://en.wikipedia.org/wiki/Integration_testing) (`npm run test-integration`) are the same `test/e2e` tests, running against *mocked* HAFAS responses from [`test/e2e/fixtures`](test/e2e/fixtures). - -1. Add a new end-to-end test that tests your feature/bugfix. -2. Make sure the test passes. You can run your test exclusively using `test.only`. -3. Record the HAFAS responses as [fixtures](https://en.wikipedia.org/wiki/Test_fixture) using `npm run test-integration:record`. -4. Make sure the passes against *only* mocked responses using `npm run test-integration`. +Refer to the [testing docs](docs/tests.md).