From 824519b0d7230f21239d30c3ca0cb461750c8425 Mon Sep 17 00:00:00 2001 From: Alex Bishop Date: Fri, 21 Feb 2025 16:48:17 +0000 Subject: [PATCH] =?UTF-8?q?BAU=20=E2=80=94=20Remove=20references=20to=20mo?= =?UTF-8?q?untebank?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per https://github.com/bbyars/mountebank mountebank is no longer maintained and the mbtest.org domain is no longer controlled by the project so remove references to it (we still suggest WireMock). --- source/testing_govuk_pay/index.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/testing_govuk_pay/index.html.md.erb b/source/testing_govuk_pay/index.html.md.erb index e7c18b54..90486b9a 100644 --- a/source/testing_govuk_pay/index.html.md.erb +++ b/source/testing_govuk_pay/index.html.md.erb @@ -72,7 +72,7 @@ You can use your test account to: - explore how the GOV.UK Pay API works - run automated [smoke tests](https://www.gov.uk/service-manual/technology/deploying-software-regularly#using-smoke-tests-after-you-deploy) -Do not use your test account for automated integration tests that run every time you change your code. Build a ‘stub’ to simulate the GOV.UK Pay API instead, using a tool like [WireMock](http://wiremock.org/) or [mountebank](http://www.mbtest.org/). +Do not use your test account for automated integration tests that run every time you change your code. Build a ‘stub’ to simulate the GOV.UK Pay API instead, using a tool like [WireMock](https://wiremock.org/). ## Testing the whole user journey