From 548d78e6eaea8bd55316cbec418b6dba297b73ee Mon Sep 17 00:00:00 2001 From: Nguyen Duc Toan Date: Tue, 6 Jun 2023 23:05:49 +0700 Subject: [PATCH] Fix broken link of MIGRATING_TO_V2.md (#1217) --- docs/MIGRATING_TO_V2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/MIGRATING_TO_V2.md b/docs/MIGRATING_TO_V2.md index 97f620485..ea9423ba5 100644 --- a/docs/MIGRATING_TO_V2.md +++ b/docs/MIGRATING_TO_V2.md @@ -391,7 +391,7 @@ Ginkgo can now repeat a test suite N additional times by running `ginkgo --repea Ginkgo requires the tests to succeed during each repetition in order to consider the test run a success. ### New: --focus-file and --skip-file -You can now tell Ginkgo to only run specs that match (or don't match) a given file filter. You can filter by filename as well as file:line. See the [Filtering Specs](onsi.github.io/ginkgo/#filtering-specs) documentation for more details. +You can now tell Ginkgo to only run specs that match (or don't match) a given file filter. You can filter by filename as well as file:line. See the [Filtering Specs](https://onsi.github.io/ginkgo/#filtering-specs) documentation for more details. ### Improved: windows support for capturing stdout and stderr In V1 Ginkgo would run windows tests in parallel with the `--stream` option. This would result in hard-to-understand interleaved output. The reason behind this design choice was that it proved challenging to intercept all stdout and stderr output on Windows. V2 implements a best-effort output interception scheme for windows that entails reassigning the global `os.Stdout` and `os.Stderr` variables. While not as bullet-proof as the Unix `syscall.Dup2` based implementation, this is likely good enough for most usecases and allows Ginkgo support on Windows to come into parity with unix.