Many integration tests fails when running against stack 240.
This morning, we update the dev-stack to 240. Many integration tests failed because the actual entity (from the backend) does not match with the expected entity in the integration tests. For example:
The modifiedOn field is 1 second different on each entity.
This issue holds up the development process in the client, and need to be addressed ASAP.
Looks like the builds for the dev branch and 1.9.0-rc branches are back to normal
Discussed with , the tests failed because syn.store always save annotations. Saving annotations change the etag and modifiedOn.
Before refactoring syn.store, we will change syn.store to always do a syn.get and return the result of syn.get. That way, the user who is using syn.store will get the most up-to-date properties of the entity.
We evaluate that syn.store takes .6s in avg without syn.get (proposed) and takes .8s with the proposed syn.get.
List of integration tests that failed:
, Thank you for the summary.
In the example (see the screenshot), there is also a new field linksTo in the returned Link. Is this field new?
Never mind, this field shows up at different location in the actual and expected values.