Netcracker / Netcracker/qubership-testing-platform-python-runner

[Feat]: Python runner takes systems for ATP from tests folder

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Shell
Stars
0
Forks
1
Avg merge
49m
Merged PRs (30d)
2

Description

Is your feature request related to a problem? Please describe

Move configuration of systems to project tests repository by path: /EnvironmentConfiguration/environment-configuration-template.json
Description of systems will be in JSON format.
Marcoses can be used in template (format ${NAME}):
CLOUD_PROTOCOL
CLOUD_PUBLIC_HOST
CURRENT_ENV_NAME
CONSUL_PUBLIC_URL
DEFAULT_TENANT_ADMIN_LOGIN
DEFAULT_TENANT_ADMIN_PASSWORD
DEFAULT_TENANT_NAME
CONSUL_ADMIN_TOKEN
Rendered value with list of systems should be saved to ENV var.
By option list of rendered systems can be saved to file.
To override template to be used should be added additional variable.

Describe the solution you'd like

It should be able to read environment variables from specific folder in repository with test cases

Describe alternatives you've considered

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Python runner entry point that handles ATP system configuration, then inspect /EnvironmentConfiguration/environment-configuration-template.json in the tests repository. Confirm how environment variables and rendered output are currently handled. Done means the runner reads and renders the template, exposes the systems through an environment variable, optionally writes them to a file, and supports a template override.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing-qa, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.