-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Update #3
Comments
Need to identify a testing plan as to where the most useful tests can be placed. A large chunk of the code base is behavioural rather than functional, i.e it requires something else to work, like the time_bucket function can only be used as part of a query. An initial testing plan is below: Unit
Integration (i.e requires a model and data to test)
All testing will be done through PyTest and will have a simple Django application configured for Timescale. It will require a timescale database instance to test against, i.e docker. |
Added more tests and better exception handling within the database expressions. Test suite is still growing and will require review. |
Tests have been added and structure for tests has been decided:
|
@schlunsen - are you able to review anything that is currently in progress, in-particular the test suites to see if i have missed anything obvious so far? |
During current work the following tasks needs to be completed:
|
Working with the package for the last year and a half now has opened up some areas where improvement is needed and required. This will be a breaking change but will allow for a more stable platform to build from.
Tasks
Potential or Investigative
The text was updated successfully, but these errors were encountered: