Generate E2E typescript test report for ReportPortal

[nallikaea]

What does this PR do?

resolves #22543

Screenshot/screencast of this PR

https://reportportal-crw.apps.ocp-c1.prod.psi.redhat.com/ui/#devspaces/launches/all

What issues does this PR fix or reference?

resolves #22543

How to test this PR?

Use REPORTER_CONSTANTS to set reporter parameters
Then run tests, for example using tests/e2e/configs/sh-scripts/regressionTestRun.sh

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix or new feature
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[dmytro-ndp]

@nallikaea : could you please share an example of ReportPortal constants to run Dev Spaces functional test suite and send test results to ReportPortal ?:

docker run --shm-size=4096m -p 5920:5920 \
 -e TS_SELENIUM_LOAD_PAGE_TIMEOUT=420000 \
 -e TS_SELENIUM_BASE_URL=https://devspaces.apps.ocp413.crw-qe.com \
 -e DELETE_WORKSPACE_ON_FAILED_TEST=true \
 -e TS_SELENIUM_START_WORKSPACE_TIMEOUT=120000 \
 -e NODE_TLS_REJECT_UNAUTHORIZED=0 \
 -e VIDEO_RECORDING=true \
 -e E2E_OCP_CLUSTER_API_URL=https://api.ocp413.crw-qe.com:6443 \
 -e TS_SELENIUM_LOG_LEVEL=TRACE \
 -e TS_WAIT_LOADER_PRESENCE_TIMEOUT=120000 \
 -e TS_COMMON_DASHBOARD_WAIT_TIMEOUT=30000 \
 -e OCP_INFRA=PSI \
 -v /tmp:/usr/local/bin:Z \
 -v /home/hudson/.kube:/home/seluser/.kube:Z \
 -v /mnt/hudson_workspace/workspace/Testing/e2e/basic/typescript-tests/test-repo/tests/e2e:/tmp/e2e:Z \
 -v /mnt/hudson_workspace/workspace/Testing/e2e/basic/typescript-tests/test-repo/tests/e2e/video:/tmp/ffmpeg_report:Z \
 -e TS_SELENIUM_VALUE_OPENSHIFT_OAUTH=true \
 -e TS_OCP_LOGIN_PAGE_PROVIDER_TITLE=htpasswd \
 -e TS_SELENIUM_OCP_USERNAME=******* \
 -e 'TS_SELENIUM_OCP_PASSWORD=******' \
 -e TS_COMMON_DASHBOARD_WAIT_TIMEOUT=120_000 \
 -e TEST_SUITE=functional-test-suite \
 -e OCP_VERSION=4.13 \
 -e ARCH_VERSION=x86_64 quay.io/eclipse/che-e2e:next

[nallikaea]

docker run --shm-size=4096m -p 5920:5920
-e TS_SELENIUM_BASE_URL=https://devspaces.apps.ocp413.crw-qe.com
-e TS_SELENIUM_LOG_LEVEL=TRACE
-v /tmp:/usr/local/bin:Z
-v /home/hudson/.kube:/home/seluser/.kube:Z
-v /mnt/hudson_workspace/workspace/Testing/e2e/basic/typescript-tests/test-repo/tests/e2e:/tmp/e2e:Z
-v /mnt/hudson_workspace/workspace/Testing/e2e/basic/typescript-tests/test-repo/tests/e2e/video:/tmp/ffmpeg_report:Z
-e TS_SELENIUM_OCP_USERNAME=*******
-e 'TS_SELENIUM_OCP_PASSWORD=******'
-e TEST_SUITE=functional-test-suite
-e OCP_VERSION=4.13
-e ARCH_VERSION=x86_64 \

-e SAVE_RP_REPORT_DATA=true
-e RP_API_KEY=<USER_APP_KEY_OR_TOKEN>
-e RP_IS_LOCAL_SERVER=false
-e RP_USE_PERSONAL=false quay.io/eclipse/che-e2e:next

[dmytro-ndp]

@nallikaea : thank you

For the sake of simplicity, I would use constant OCP_INFRA=["PSI", "AWS", "IBM Z", "IBM Power"] instead of ARCH_VERSION.

The point is that when it turns to CRW Jenkins CI, typescript-tests pipeline is running tests using x86_64 Jenkins nodes doesn't matter if the testing OCP arch is amd64, or s390x.
The only difference is value of OCP_INFRA parameter of typescript-tests pipeline.

[nallikaea]

@nallikaea : thank you

For the sake of simplicity, I would use constant OCP_INFRA=["PSI", "AWS", "IBM Z", "IBM Power"] instead of ARCH_VERSION.

The point is that when it turns to CRW Jenkins CI, typescript-tests pipeline is running tests using x86_64 Jenkins nodes doesn't matter if the testing OCP arch is amd64, or s390x. The only difference is value of OCP_INFRA parameter of typescript-tests pipeline.

okay, replaced in new commit

[dmytro-ndp]

From security perspective I would prefer empty RP user name by default.

[dmytro-ndp]

@nallikaea : thanks for the fixup.

I tried to run tests with parameters you shared [1] and using personal RP access token [2], but had got an error:

01:10:18  Error: Request failed with status code 403: {"errorCode":4003,"message":"You do not have enough permissions."}
01:10:18  URL: https://reportportal-crw.apps.ocp-c1.prod.psi.redhat.com/api/v1/superadmin_personal/launch
01:10:18  method: POST
01:10:18      at /tmp/e2e/node_modules/@reportportal/client-javascript/lib/rest.js:41:15
01:10:18      at processTicksAndRejections (node:internal/process/task_queues:96:5)

It seemed to be missing -e RP_USER in the test run command.

[1] #22590 (comment)
[2] https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/Testing/job/e2e/job/basic/job/typescript-tests/13528/consoleFull

[dmytro-ndp]

@nallikaea : second try with RT_USER parameter and single testcase was successful: https://reportportal-crw.apps.ocp-c1.prod.psi.redhat.com/ui/#devspaces/launches/all/132 , https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/Testing/job/e2e/job/basic/job/typescript-tests/13529/console

At the same time I couldn't find info about test OCP version = 4.14 and OCP infra = PSI in RP test launch.
Is it expected?
Test run command:

docker run --shm-size=4096m -p 5920:5920 -e TS_SELENIUM_LOAD_PAGE_TIMEOUT=420000 -e TS_SELENIUM_BASE_URL=https://devspaces.apps.ocp414.crw-qe.com/ -e DELETE_WORKSPACE_ON_FAILED_TEST=true -e TS_SELENIUM_START_WORKSPACE_TIMEOUT=120000 -e NODE_TLS_REJECT_UNAUTHORIZED=0 -e VIDEO_RECORDING=true -e E2E_OCP_CLUSTER_API_URL=https://api.ocp414.crw-qe.com:6443/ -e TS_SELENIUM_LOG_LEVEL=TRACE -e TS_WAIT_LOADER_PRESENCE_TIMEOUT=120000 -e TS_COMMON_DASHBOARD_WAIT_TIMEOUT=30000 -e OCP_INFRA=PSI -e OCP_VERSION=4.14 -v /tmp:/usr/local/bin:Z -v /home/hudson/.kube:/home/seluser/.kube:Z -v /mnt/hudson_workspace/workspace/Testing/e2e/basic/typescript-tests/test-repo/tests/e2e:/tmp/e2e:Z -v /mnt/hudson_workspace/workspace/Testing/e2e/basic/typescript-tests/test-repo/tests/e2e/video:/tmp/ffmpeg_report:Z -e USERSTORY=SmokeTest -e TS_SELENIUM_OCP_USERNAME=***** -e 'TS_SELENIUM_OCP_PASSWORD=*****' -e SAVE_RP_REPORT_DATA=true -e RP_IS_LOCAL_SERVER=false -e RP_USE_PERSONAL=false -e RP_USER=DNOCHEVN ******** quay.io/eclipse/che-e2e:next

Third run, now with -e TEST_SUITE=functional-test-suite, has left no test launch in RP at all: https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/Testing/job/e2e/job/basic/job/typescript-tests/13530/consoleFull

[nallikaea]

no, you should not set RP_user by default, let me check

[dmytro-ndp]

looks good to merge