Skip to content

Conversation

MarleneKress79789
Copy link
Contributor

@MarleneKress79789 MarleneKress79789 commented Jul 7, 2023

All Submissions:

  • Is the title of the Pull Request correct?
  • Is the title of the corresponding issue correct?
  • Have you updated the changelog?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Are you mentioning the issue which this PullRequest fixes ("Fixes...")
  • Before you merge don't forget to run all tests for all Exasol version, by adding [run all tests] to the commit message
  • Are the CLI usage examples up to date?

fixes #359
fixes #322

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would put these directly into test_env_variable.py, because they are very test specific



class UsedLogPath:
def __init__(self, log_path: Path, task_input_parameter):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think, you could directly fetch these parameters from the task

return f"Logging: {used_log_path.task_input_parameter}" in log_content

def __repr__(self):
return f"LogPathCorrectnessMatcher({str(self.expected_log_path)})"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The representation should be designed in a way, that you can potentially diff them, because they are used in diff in case of a failing assert

self.task_input_parameter = task_input_parameter

def __repr__(self):
return f"UsedLogPath({str(self.log_path)}, {self.task_input_parameter})"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The representation should be designed in a way, that you can potentially diff them, because they are used in diff in case of a failing assert

Co-authored-by: Torsten Kilias <[email protected]>
@MarleneKress79789 MarleneKress79789 enabled auto-merge (squash) July 13, 2023 11:52
@MarleneKress79789 MarleneKress79789 merged commit d6fcbaa into main Jul 13, 2023
@MarleneKress79789 MarleneKress79789 deleted the bug/322_test_LOG_ENV_VARIABLE_NAME branch July 13, 2023 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Configuration of logging fails if the path in LOG_ENV_VARIABLE_NAME does not exist Add test for the environment variable LOG_ENV_VARIABLE_NAME

2 participants