Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple configurations #13

Open
jevgenijSy opened this issue Aug 17, 2020 · 2 comments
Open

Multiple configurations #13

jevgenijSy opened this issue Aug 17, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@jevgenijSy
Copy link
Contributor

jevgenijSy commented Aug 17, 2020

Hello,
I would like to configurate multiple mappings for test_suite and test_case, for instance:

...
      "mappings": {
        "test_suite":[ {
          "key": "suite1",
          "name": "%fields.customfield_13050|default=unnamed%",
          "settings": {
            "resources": [
              "../${RELATIVE_ROOT_PATH}init.robot"
            ],
            "suite_setup": [
              "Init Suite Keyword"
            ],
            "test_setup": [
              "Init Test Keyword"
            ],
            "test_teardown": [
              "Teardown Keyword"
            ]
          }
        },
        {
          "key": "suite2",
          "name": "%fields.customfield_13050|default=unnamed%",
          "settings": {
            "resources": [
              "../${RELATIVE_ROOT_PATH}init2.robot"
            ]
          }
        }
      ]}

And use them maybe via an option on Jira?... is it possible to implement?

@skiera
Copy link
Owner

skiera commented Aug 17, 2020

Hi,

we used different configuration files within the project, but I will check if I can implement conditions.

Regards,
Sven

@skiera skiera self-assigned this Aug 17, 2020
@skiera skiera added the enhancement New feature or request label Aug 17, 2020
@jevgenijSy
Copy link
Contributor Author

jevgenijSy commented Aug 17, 2020

I Figured it out!

{
  "source": {
    "example1": {
      "type": "jira",
...
    },
    "example2": {
      "type": "jira",

This is how the "keys" for configs and credentials are provided
And then you just have to call robotizr twice

python -m robotizr -c ${PATH_TO_PROJECT}/config/robotizr-config.json ${HOME}/secure/private.json -s example1 -t ${PATH_TO_PROJECT}\cases --query "project = EXMAPLE AND type = example1"
python -m robotizr -c ${PATH_TO_PROJECT}/config/robotizr-config.json ${HOME}/secure/private.json -s example2 -t ${PATH_TO_PROJECT}\cases --query "project = EXMAPLE AND type = example2"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants