counterweight/data-xexe
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

more readme stuff

Browse source
This commit is contained in:
Pablo Martin 2024-06-13 18:03:46 +02:00
parent cf24605e44
commit 55ef7ab273
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -157,7 +157,7 @@ This tool was made specifically to feed our DWH. These are the steps to perform
## Testing ## Testing
This CLI app has three groups of tests: This CLI app has three groups of automatic tests:
- `tests_cli`: simulate calling the CLI to check proper calls, not much attention paid to actual results. - `tests_cli`: simulate calling the CLI to check proper calls, not much attention paid to actual results.
- `tests_unit`: unit tests for some domain-heavy parts of the codebase. - `tests_unit`: unit tests for some domain-heavy parts of the codebase.
@ -165,4 +165,6 @@ This CLI app has three groups of tests:
You can run everything with `pytests tests`, or narrow it down more if you want to. You can run everything with `pytests tests`, or narrow it down more if you want to.
There is a special test in `tests_integration` that runs against the real xe.com API. This tests is commented out to avoid repeteadly consuming API hits. You can use by uncommenting it manually. I know it's annoying, but then again, it shouldn't to be very annoying since you should only use that test sparingly. There is a special test in `tests_integration` that runs against the real xe.com API. This tests is commented out to avoid repeteadly consuming API hits. You can use by uncommenting it manually. I know it's annoying, but then again, it shouldn't to be very annoying since you should only use that test sparingly. Also no pressure, but if you leave that uncommented, you might end up creating a massive problem and breaking production.
Also, FYI, there are currently no automated tests for writing against a Postgres database.