Review test approach for VUU

[naleeha]

Feature Request

Description of Problem:

1. Hard to write a unit test for things like data providers in the examples. Currently data providers cover

• Source the data
• Map the data to TableRow
• Update table
  In the scenario tests, the providers are mocked so we can provide test data different from the source. This skips testing of some of the internal functionalities.

2. We don't have a way to test end to end of the VUU server (e.g. the bootstraping/configurisation code)

3. We need test that would fail if core function is broken e.g. should not be able to deploy to the demo environment if it doesn't test basic test like ui cannot load.

• End to end test across server and ui
• Need to have single way of building the project locally and on demo pipeline so cannot get in situation where it works in one env but not the other

Potential Solutions:

• Add end-to-end/acceptance style test to automate a black box test. Need to include the code that startup the VUU server code and create input and then assert on the output as if some one is using it

• Extend the current test framework to support join table testing

  • Join tables are updated by updating the underlying table and subscribing to the update
  • The testing framework currently doesn't support the update to join tables

• For unit testing data providers - separate data sourcing from data providers

  • It would be good to separate data sourcing so that they can be mocked and include real data providers in the test.
  • We could introduce contract testing with the data source & mapping to internal model separately
  • Questions - what is responsibility of RPC handler implementation (services in basket examples) vs Data Provider - is data provider for just initialising DataTable & mange update from the source vs RPC handlers manipulate DataTable based on user updates?