From 55ef7ab273465d83d45f6916b6c00af8fa33a731 Mon Sep 17 00:00:00 2001 From: Pablo Martin Date: Thu, 13 Jun 2024 18:03:46 +0200 Subject: [PATCH] more readme stuff --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c883941..396d7d7 100644 --- a/README.md +++ b/README.md @@ -157,7 +157,7 @@ This tool was made specifically to feed our DWH. These are the steps to perform ## 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_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. -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.