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
I think in the long run, any push or merge into master should have a hook to run all unit tests. I'm not sure if we need that level of protection for development, but it's definitely open for discussion
The SQLDriver unit tests will be a monster by the time they are done, including spooling up of docker. I would imagine these tests will end up taking over a minute or so by the time they are done
It'll be a huge improvement from current by-hand testing all the different database examples via forms.
To test dependent handling we'll probably want a testing database/form/docker images that has dependents. Do you have a preference on a sample database? Create our own, or use use Northwind, AdventureWorks, Chinook?
On Thu, Apr 13, 2023, 10:14 AM ssweber ***@***.***> wrote:
It'll be a huge improvement from current by-hand testing all the different
database examples via forms.
To test dependent handling we'll probably want a testing
database/form/docker images that has dependents. Do you have a preference
on a sample database? Create our own, or use use Northwind, AdventureWorks,
Chinook?
—
Reply to this email directly, view it on GitHub
<#278 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQX2REVQZO44LMLZ3HWXRPTXBAC5XANCNFSM6AAAAAAW4N3FEQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
On Thu, Apr 13, 2023, 11:01 AM Jon Decker ***@***.***> wrote:
It really doesn't matter to meet too much. Docker is probably the easiest
since we already have everything in place to use them.
On Thu, Apr 13, 2023, 10:14 AM ssweber ***@***.***> wrote:
> It'll be a huge improvement from current by-hand testing all the
> different database examples via forms.
>
> To test dependent handling we'll probably want a testing
> database/form/docker images that has dependents. Do you have a preference
> on a sample database? Create our own, or use use Northwind, AdventureWorks,
> Chinook?
>
> —
> Reply to this email directly, view it on GitHub
> <#278 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AQX2REVQZO44LMLZ3HWXRPTXBAC5XANCNFSM6AAAAAAW4N3FEQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
Activity
ssweber commentedon Apr 13, 2023
Yes, I'd love this. I've never created a test-suite before.
If you create a few, I'll start helping out.
refs #278 First bits of unit testing set up
refs #278 Unit Test example for ProgressAnimate
PySimpleSQL commentedon Apr 13, 2023
I think in the long run, any push or merge into master should have a hook to run all unit tests. I'm not sure if we need that level of protection for development, but it's definitely open for discussion
The SQLDriver unit tests will be a monster by the time they are done, including spooling up of docker. I would imagine these tests will end up taking over a minute or so by the time they are done
ssweber commentedon Apr 13, 2023
It'll be a huge improvement from current by-hand testing all the different database examples via forms.
To test dependent handling we'll probably want a testing database/form/docker images that has dependents. Do you have a preference on a sample database? Create our own, or use use Northwind, AdventureWorks, Chinook?
PySimpleSQL commentedon Apr 13, 2023
PySimpleSQL commentedon Apr 13, 2023
refs #278 Unit Test example for ProgressAnimate
refs #278 Unit Test example for ProgressAnimate
refs #278 Unit Tests ruff ignore
refs #278 fix ruff error
refs #278 fix ruff error
refs #278 fix ruff error
refs #278 fix ruff errors
Squashed commit of the following:
Squashed commit of the following: