Out of interest in the project in making some improvements, I was attempting to baseline myself with the code base, environment dependencies, and ability to run UTs.
def test_load_metrics_from_file(metrics_info):
data = load_metrics_from_file(METRICS_FILENAME)
(snip)
...
METRICS_FILENAME is set
$ python3
Python 3.5.2 (default, Nov 12 2018, 13:43:14)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import metrics
>>> metrics.METRICS_FILENAME
'.metrics'
hm... I know that a .metrics temp file is generated after running metrics on a project code base ... but the tests seem to rely upon this dependency?
Out of interest in the project in making some improvements, I was attempting to baseline myself with the code base, environment dependencies, and ability to run UTs.
Forked into: https://github.com/mcallaghan-bsm/metrics/tree/wip_poc_pipenv_and_pytest_run_v0.3.3
Which has the new
pipenv
Pipfile bits for easier environment setup, enabling magic:Then in theory we're setup and ready to go. Let's try to run the tests off the latest version forked on August 9th 2019 (v0.3.3)
Darn, so there is supposed to be a
.metrics
file kicking around in test resources? (indeed not therefind tests/resources/| grep metric
is empty)Which test does it come from?
https://github.com/finklabs/metrics/blob/master/tests/test_metrics_utils.py#L87
METRICS_FILENAME
is sethm... I know that a
.metrics
temp file is generated after running metrics on a project code base ... but the tests seem to rely upon this dependency?