36 track changes of case

[stanislaw-zakrzewski]

No description provided.

[codecov-commenter]

Codecov Report

Merging #37 (fddec66) into main (2f5a8f1) will increase coverage by 17.60%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##             main      #37       +/-   ##
===========================================
+ Coverage   65.76%   83.37%   +17.60%     
===========================================
  Files         146       36      -110     
  Lines        4493     1221     -3272     
  Branches     1352      317     -1035     
===========================================
- Hits         2955     1018     -1937     
+ Misses       1538      203     -1335     

Files	Coverage Δ
data-serving/data-service/src/controllers/case.ts	76.50% <100.00%> (ø)
data-serving/data-service/src/index.ts	85.88% <100.00%> (ø)
data-serving/data-service/src/model/day0-case.ts	90.90% <100.00%> (+0.16%)	⬆️

... and 110 files with indirect coverage changes

[jim-sheldon]

The 0th revision looks like the new case itself...should this test check for the first revision, i.e. the result of the PUT request?

Following the Mongo document versioning pattern this would mean checking the cases collection and revisions collection.

[stanislaw-zakrzewski]

In this test case we compare a case before update to the case revision that was crated during the update.
So at the beginning of this test we create a new case c. Then we send a request to update the content of this case, thus generating a new case revision based on case c. We then compare case c with case saved in case revision. The result from PUT request will contain an updated case.

The revision numbering might be a little odd. After creating case gets 0 as revision number, and after an update this number is incremented by 1.