From 4f78a698c2c3a36b2957c3215de33ca0d47e27ae Mon Sep 17 00:00:00 2001 From: zhou-yinyuan Date: Wed, 14 Aug 2024 17:20:38 +0800 Subject: [PATCH] Solution of e2e timed issue [docs]: fix issue --- .../en/issue-solutions/solution-of-e2e-timed-issue.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/src/content/docs/en/issue-solutions/solution-of-e2e-timed-issue.mdx b/docs/src/content/docs/en/issue-solutions/solution-of-e2e-timed-issue.mdx index f019f3f63..f54998fe7 100644 --- a/docs/src/content/docs/en/issue-solutions/solution-of-e2e-timed-issue.mdx +++ b/docs/src/content/docs/en/issue-solutions/solution-of-e2e-timed-issue.mdx @@ -62,16 +62,16 @@ When running the e2e tests, all e2e tests failed because we can't get build data None - 2. For the e2e test about import from config file, change the config file name to the e2e test config file name, and replace origin input-files/*.template.json file - If we directly use the origin file name, we will not need to modify the code. And we only upload input-files/*.template.json file to repo rather than input-files/*.json, so we must modify the *.template.json file + 2. For the e2e test about import from config file, change the config file name to the e2e test config file name, and replace origin input-files/*.template.json file + If we directly use the origin file name, we will not need to modify the code. And we only upload input-files/*.template.json file to repo rather than input-files/*.json, so we must modify the *.template.json file - 3. In the *.template.json file, for data security, we must replace token with placeholder of <E2E_TOKEN_JIRA> , <E2E_TOKEN_BUILD_KITE>，<E2E_TOKEN_GITHUB> like the previous file + 3. In the *.template.json file, for data security, we must replace token with placeholder of <E2E_TOKEN_JIRA> , <E2E_TOKEN_BUILD_KITE>，<E2E_TOKEN_GITHUB> like the previous file We can copy the previous placeholder to use the new placeholder, And when we run pnpm e2e:local, the generate-config-files.sh file will replace the placeholder with the real token. Tips: there is an e2e test to test the pipeline that is no organization in the unhappy path, and the placeholder is <E2E_TOKEN_PIPELINE_NO_ORG_CONFIG_BUILDKITE>, maybe you need to check if the token is correct 4. Modify local token file. We will modify the origin token to the new token in the .env.local file to ensure that the e2e test can be passed locally - In the local, the placeholder from the *.template.json file will be replaced with the token in the .env.local file. And the generate-config-files.sh file will create a new json file with the same name by *.template.json file. + In the local, the placeholder from the *.template.json file will be replaced with the token in the .env.local file. And the generate-config-files.sh file will create a new json file with the same name by *.template.json file. 5. Run the e2e test, and change the report data and local csv files by the Step 1 @@ -87,7 +87,7 @@ When running the e2e tests, all e2e tests failed because we can't get build data 8. Close the playwright and rerun the cmd of pnpm e2e:local to re-test the e2e test - The reason is to ensure that all e2e tests are passed in the local env. Becausethe changes of *.template.json will not be hot replacement, however, when we run the pnpm e2e:local command, the json file will be generated by generate-config-files.sh file + The reason is to ensure that all e2e tests are passed in the local env. Becausethe changes of *.template.json will not be hot replacement, however, when we run the pnpm e2e:local command, the json file will be generated by generate-config-files.sh file Step 3. Modify the remote env to ensure that all e2e tests are passed in the remote env