testing_tools | Tools for testing AbanteCart ecommerce

Two ways I've found to fix:

1. Change the name of the conda environment. Just cloning sandbox to boxsand did the trick
2. Add python.condaPath variable to VSCode's preferences

The solution is to create a .env file to set the src folder in PYTHONPATH otherwise pytest is unable to find the model package. Also, putting conftest.py inside the src folder doesn't help as suggested by someone.

It turned out that it was necessary to create an (empty) __init__.py - file also in the "tests"-directory, i.e the one where my test-Python-files lie.

Weirdly enough, for unittest it's sufficient to only insert an (empty) __init__.py into the module-folder to be tested, but not where the test scripts are located (in my case in "tests", see directory tree in my initial question above). This made sense to me, as the testing scripts import the scripts being tested, so the latter need to be importable as modules. Yet, for some reason, pytest requires the (empty) __init__.py - file to be (also) in the folder with the testing scripts (called "tests" in my case).

As an aside, what sparked the idea of trying that out was the following lines while I was reading through testing with python using VS Code:

Tip: Sometimes tests placed in subfolders aren't discovered because such test files cannot be imported. To make them importable, create an empty file named init.py in that folder.

Two Issues:

• where does the difference come from
• how to apply the epsilon?

Boost Multiprecision uses template expressions to defer evaluation.

Also, you're choosing some rational fractions that cannot be exactly represented base-10 (cpp_dec_float uses decimal, so base-10).

This means that when you do

You are probably actually invoking different Python interpreters/environments in each methods. VSCode docs say:

By default, the Python extension looks for and uses the first Python interpreter it finds in the system path.

But there are several ways of overriding this, manually selecting the interpreter is the most obvious.

To debug, I suggest you temporarily put the following lines at the very top of run_adapter.py (might wanna back it up first, as it is part of the VS-code Python extension):

I found the solution by looking up the pytest syntax:
just use--ignore=backup and it will work