Redefine integration tests

nj1973 commented 11 months ago

We have the existing test framework, a lot of which should be retained.

These are the thoughts in my head that I'm capturing here:

I'd like to get away from our reliance on pre-built schemas. Each set of tests should create its own test tables with minimal data. We need to bare in mind future requirements for matching SQL Server/Teradata test tables too.
There's no TeamCity anymore
DVT tests run in Cloud Build Run, perhaps that's something we could imitate?
Cody has some good ideas regarding testing
I'd like to make the stories self sufficient and not rely on an existing SH schema

nj1973 commented 11 months ago

Any unit tests that were really integration tests were dropped into tests/integration/ - but untested. These will need fixing during this work.

nj1973 commented 10 months ago

I think including stories in this issue will be too onerous. We should have this issue for tests/integration/ tests and have a new issue for stories (tests/stories?)

nj1973 commented 10 months ago

I've created issue https://github.com/gluent/goe/issues/35 for the stories, this issue can focus on the module based integration tests.

gluent / goe

Redefine integration tests #17