nodejs-integration-tests-best-practices icon indicating copy to clipboard operation
nodejs-integration-tests-best-practices copied to clipboard

Published 20 hours ago • verified publisher icon testjavascript

Enrich our DB model

Open goldbergyoni opened this issue 4 years ago • 2 comments

The example app DB schema is too simplistic and might not tell the truth when conducting performance benchmarks. It could be great to add a few more fields to the main table and also one more relation.

Before picking this issue, it's recommended to have a short tech planning chat here and only then upon sync to get up to speed.

goldbergyoni avatar Dec 08 '20 15:12 goldbergyoni

There are levels of data that we should have:

  • Test data - Orders - Rows that are modified by the tests - Created per test - We have this
  • Context - StoreInfo - Rows that are related to the test but not modified by the test - Created per suite - We need this
  • Metadata - Countries - Rows that just serve as global enums and supporting data - Created once - We need this

goldbergyoni avatar Feb 05 '21 08:02 goldbergyoni

@goldbergyoni @DanielGluskin Is this still an issue/was this ever worked on?

I'm interesting in contributing to this repo, since it did so much for me.

philipeatela avatar Sep 29 '21 15:09 philipeatela