Description

Created a bash script and a script to move test-results to a central location.

Fixes #143
Organise report after running a test

Type of change

• Enhancement (non-breaking change which improves an existing functionality).

Detailed scenario

N/A

Technical description

Documentation

You can move the test-results folder for only two test so far(smoke and e2e test). To move the test-results directory after running your test, you need to add a tag parameter without it the test-results won't be move or rename.
Example --
npm run test:smoke --tag= WPR3.17.4_e2e1.0.0
npm run test:e2e --tag= WPR3.17.4_e2e1.0.0

After the test is complete the test-results folder would be rename to WPR3.17.4_e2e1.0.0 and moved to the central localtion(/var/shared/rocket-e2e-reports)

Note -- Without the tag parameter the test-reports won't be move or rename.

Mandatory Checklist

Code validation

• I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I implemented built-in tests to cover the new/changed code.

Code style

• I wrote a self-explanatory code about what it does.
• I protected entry points against unexpected inputs.
• I did not introduce unnecessary complexity.
• Output messages (errors, notices, logs) are explicit enough for users to understand the issue and are actionnable.