Add basic import test

[Hartorn]

Description

Related Issue

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make codestyle.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.

[andreybavt]

why are we still using poetry if there's PDM?

[Hartorn]

Test before was with poetry, and habits die hard ^^'
Can change, have to see how to create empty project with pdm

[andreybavt]

I'd actually only use pdm to create a virtualenv (since pdm is already installed anyway)
pdm venv create XXX

and then activate it and install giskard with regular pip

pip install "$(ls ../dist/*.whl)[server]"
python -c 'import giskard'

[rabah-khalek]

this makes it way more readable too

[andreybavt]

and closer to what people will do

[andreybavt]

I'd still skip the pdm init as we don't need a project to be create just simple venv:

pdm venv create --name test-install
eval $(pdm venv activate test-install)
pip install "$(ls ../dist/*.whl)"
python -c "import giskard"

after the second line in the script you shouldn't need to use pdm to run python

[andreybavt]

could you rename this step to "Create new project and install server wheel (Poetry)"

[Hartorn]

Done

[andreybavt]

please also add Poetry to the step name

[andreybavt]

to make it clear what is going on let's mention pdm/pip/poetry in step names

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information