952 days continuous production uptime, 40k+ tp/s single node. Original corpo Bitbucket history not included — clean archive commit.
22 lines
889 B
Markdown
22 lines
889 B
Markdown
Unit Tests
|
|
==========
|
|
Everyone's favorite subject, amirite?
|
|
|
|
So, if you're wanting to get started with the developer unit tests instead of writing your own,
|
|
feel free to use/borrow/steal these.
|
|
|
|
In the ./tests/unit/data directory you'll find dumps for both mySQL and mongoDB tables.
|
|
|
|
Note that unit tests use the gaTest_tst collection/table in both schemas. For mongoDB, the collection
|
|
is created in the {env}_givva_namaste database. (Not the admin db!)
|
|
|
|
Unit test require a somewhat significant amount of data. Still, even these data files may not
|
|
provide you with the stretch room you need. If you get a unit test that fails, try running the test
|
|
again. Often times, there just wasn't enough data to meet the query criteria for the test.
|
|
|
|
Note that, for every dev merge into master, all unit tests are run until all are green prior to the merge.
|
|
|
|
--Micheal Shallop
|
|
|
|
On Jul 25, 2018
|