Integration Tests: adds runtime version skew tests

[JoshVanL]

Adds v1.13 binary building for integration tests. Integration test cases can now execute tests with v1.13 runtime binaries, making it possible to assert version skew scenarios in custom cases.

As we release new versions, we can add to this list of binaries to support version skew testing. By default, current tree code binaries will continue to be used.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.81%. Comparing base (091a204) to head (0f1d849).
Report is 6 commits behind head on master.

❗ Current head 0f1d849 differs from pull request most recent head cb1c445

Please upload reports for the commit cb1c445 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7575      +/-   ##
==========================================
+ Coverage   61.39%   61.81%   +0.41%     
==========================================
  Files         265      245      -20     
  Lines       22609    22420     -189     
==========================================
- Hits        13880    13858      -22     
+ Misses       7579     7398     -181     
- Partials     1150     1164      +14     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cicoyle]

Is the goal for your skew test PR to eventually write all future version skew tests, and keep adding those files in this manner? Or just for one off testing people can update these values?

Im wondering if the version should be parameterized here or if we should make this file name indicative that its for 1.13

[JoshVanL]

Yes, the idea is that we would keep adding to these tests as and when. We can create things like previous enums if we want.

[cicoyle]

This will be really nice to use for future versions. Thanks Josh 🚀

[mukundansundar]

Nice addition Josh. Is there a way where we need not repeatedly add the main.go for each future version?

Can we have /previous as a constant and get the previous version to test with as a workflow parameter say 1.13.0 ...
Then we can download the 1.13 source code and build the ITs from that?
OR only the go.mod and keep the daprd, injector etc services main.go constant for all previous versions as of now since we do not have any changes?

[JoshVanL]

Nice addition Josh. Is there a way where we need not repeatedly add the main.go for each future version?

Can we have /previous as a constant and get the previous version to test with as a workflow parameter say 1.13.0 ... Then we can download the 1.13 source code and build the ITs from that? OR only the go.mod and keep the daprd, injector etc services main.go constant for all previous versions as of now since we do not have any changes?

There is no great workaround here as the go.mod relies on the main entry point existing to resolve. We also cannot download the code during runtime as this requires downloading assets from the internet during execution of the test. While a bit annoying to need to create mains for every release, I don't think it's a huge amount of work we need to stress over doing 3/4 times a year.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.81%. Comparing base (091a204) to head (0f1d849).
Report is 8 commits behind head on master.

❗ Current head 0f1d849 differs from pull request most recent head 2052859

Please upload reports for the commit 2052859 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7575      +/-   ##
==========================================
+ Coverage   61.39%   61.81%   +0.41%     
==========================================
  Files         265      245      -20     
  Lines       22609    22420     -189     
==========================================
- Hits        13880    13858      -22     
+ Misses       7579     7398     -181     
- Partials     1150     1164      +14     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.