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

Feature/test coverage improval #4

Closed
wants to merge 21 commits into from
Closed

Feature/test coverage improval #4

wants to merge 21 commits into from

Conversation

MarcoHuebner
Copy link
Collaborator

@MarcoHuebner MarcoHuebner commented Jul 8, 2023

Pull request contains suggestion/ solution for #1 (and reintroduces the version test for compatibility with the version specified in the sphinx doc), increases test coverage to >95%, and is compatible with previous PR.

resolves #1 , resolves #24

@MarcoHuebner MarcoHuebner self-assigned this Jul 8, 2023
@pmayd
Copy link
Collaborator

pmayd commented Sep 12, 2023

I will try to review this PR before the next project cycle begins, totally forgot about this, sorry!

README.md Outdated Show resolved Hide resolved
docs/source/conf.py Outdated Show resolved Hide resolved
docs/source/contribute.rst Outdated Show resolved Hide resolved
tests/rsc/data.zip Outdated Show resolved Hide resolved
Copy link
Collaborator

@pmayd pmayd left a comment

Choose a reason for hiding this comment

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

LGTM

I see now that you are using the new test data in the new test files so good by me! I did not test it locally but I guess we can talk more about it once we have merged it and see what is still missing. Would be nice to understand which .rst files are autogenerated and which ones have to be maintained manually, though!

This test currently serves no purpose, since there are no Sphinx
documentation variables to test.
@MarcoHuebner

This comment was marked as outdated.

@MarcoHuebner
Copy link
Collaborator Author

MarcoHuebner commented Nov 1, 2023

TODO: Double-check config tests, since they seem to mess with the settings.ini in undesired ways - DO NOT MERGE YET

@pmayd
Copy link
Collaborator

pmayd commented Nov 1, 2023

That is unlikely as I tested this several times and my local config was never changed but maybe You can describe your observations. It is a little tricky to test this but the tests should use a temporary folder and config and not your local one

@MarcoHuebner
Copy link
Collaborator Author

The config_dir in the settings.ini was/ is pointing to a local, temporary pytest directory (...\AppData\Local\Temp\pytest-of-...\pytest-222\.pystatis18) after running pytest. I haven't investigated the behavior in detail yet, but I suppose it results from the config_dir fixture and one of the create_settings calls incorrectly overwriting the "real" settings.ini.

Is the settings still used in the when #20 is addressed? Otherwise, this could be ignored.

@pmayd
Copy link
Collaborator

pmayd commented Nov 1, 2023

The config_dir in the settings.ini was/ is pointing to a local, temporary pytest directory (...\AppData\Local\Temp\pytest-of-...\pytest-222\.pystatis18) after running pytest. I haven't investigated the behavior in detail yet, but I suppose it results from the config_dir fixture and one of the create_settings calls incorrectly overwriting the "real" settings.ini.

Is the settings still used in the when #20 is addressed? Otherwise, this could be ignored.

We don't use a settings.ini any more, everything is directly stored in the config.ini

But I just realize I might have made an error and we need it.... Once you finish your session the information is lost where to find the new config file that is stupid from my side so I actually need the settings.ini again ...

Maybe we can just omit the feature that you can configure your own config dir

Update tests for the new config and settings

# 4
@MarcoHuebner
Copy link
Collaborator Author

Continued from internal branch in #45

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.

Add Test Coverage and "Documentation Building" Badge to README Rewrite test_version
2 participants