From c2fcc1d79826a0a1ba80a14f5b09a67d3a84857e Mon Sep 17 00:00:00 2001 From: Cedd Burge Date: Wed, 17 May 2023 18:20:49 +0100 Subject: [PATCH] Update to cypress/included:12.4.1 This fixes the problem in https://github.com/cypress-io/cypress-docker-images/issues/747 --- Dockerfile.cypress | 2 +- README.md | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/Dockerfile.cypress b/Dockerfile.cypress index efe22ff..139f03e 100644 --- a/Dockerfile.cypress +++ b/Dockerfile.cypress @@ -1,4 +1,4 @@ -FROM cypress/included:12.4.1 +FROM cypress/included:12.12.0 COPY cypress.config.js ./ COPY ./cypress ./cypress diff --git a/README.md b/README.md index 17a40be..a744ed0 100644 --- a/README.md +++ b/README.md @@ -54,3 +54,7 @@ You will need to create a (free) Netlify account if you haven't already got one, The [usage_scenario.yml](./usage_scenario.yml) file is used with the [Green Metrics Tool](https://metrics.green-coding.berlin/index.html) from Green Coding Berlin to analyse how much carbon is emitted when using the website. It tracks the emissions from running the cypress tests, which visit every page in the website, so effects of changes can be easily monitored. The lambda and the calls the the google api are not included in this. You can see some results on the [Green Metrics Tool webiste](https://metrics.green-coding.berlin/stats.html?id=ad7de4a7-9a63-4970-ac00-3bea04843d1b) + +The usage_scenario.yml has a very similar format to the usage_scenario.yml, so you can run `docker compose up --build --abort-on-container-exit --exit-code-from cypress` to debug locally. + +Submitting runs is currently a manual process, and can be done using the [Certify New Software form](https://metrics.green-coding.berlin/request.html).