You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code coverage is currently only 87%, but with several files well below that coverage. The idea is to leave the overall coverage above 90% and also for each file.
Need:
This way we will have much better confidence about any future changes that are made to the code. Facilitating its evolution.
Implementation:
Continue test implementation as is.
The text was updated successfully, but these errors were encountered:
Hi @richecr I'd like to give it a shot. Is duck_orm/model_manager.py a good starting point as it has the lowest coverage?
Also can you please tell me more about the approach followed in create_table function inside duck_orm/model_manager.py when I tried to write a test case for coverage it was giving errors.
Hi @sunny-Ne5, it's great that you are interested in the project.
duck_orm/model_manager.py is a good start.
The create_table method is being removed from this project and migrated to duck-orm-cli to handle migrations in a separate project, so the method is not working. Thanks for letting me know, I'll remove the migrated code.
And I will be very happy to receive your contributions. And I will be very happy to receive your contributions. Therefore, if you prefer, you can test the other functions and ignore the ones: get_database, create_table, drop_table and _execute_sql
Feature description::
Code coverage is currently only 87%, but with several files well below that coverage. The idea is to leave the overall coverage above 90% and also for each file.
Need:
This way we will have much better confidence about any future changes that are made to the code. Facilitating its evolution.
Implementation:
Continue test implementation as is.
The text was updated successfully, but these errors were encountered: