test: Fir 29921 add inf and nan tests to python sdk

[stepansergeevitch]

• refactored out common unit tests into common module
• added unit and integration tests for inf and nan values

[ptiurin]

Is there a reason to change this? It's scoped to session if we need to reuse the database, but it's not autoused so only relevant tests will invoke it.

[stepansergeevitch]

This fixture failed for me since it's using connection_system_engine_no_db, which itself is per test scoped. This causes pytest to fail. I'm not sure how it used to work and if it's related to my changes. I'll take a look

[stepansergeevitch]

This is the error I get locally on the main now: ScopeMismatch: You tried to access the function scoped fixture connection_system_engine_no_db with a session scoped request object, involved factories:

[stepansergeevitch]

It works on github CI because currently the use_database test (which is the one that uses this fixture) is skipped for staging

[ptiurin]

I see. That's annoying :(
My worry here is if we reuse this fixture it might run into race condition when one test is trying to delete a db and another one to use it. Maybe let's add a few random numbers just to be safe?

[stepansergeevitch]

Integration tests are passing: https://github.com/firebolt-db/firebolt-python-sdk/actions/runs/7869763880

[ptiurin]

Otherwise lgtm

[ptiurin]

I see. That's annoying :(
My worry here is if we reuse this fixture it might run into race condition when one test is trying to delete a db and another one to use it. Maybe let's add a few random numbers just to be safe?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud