Add test for integration BC.

[dereuromark]

We would like to use an active demo project to verify that integration of the latest propel code as well as PRs work without unknown or hidden bc breaks. So this check may fail, if BC breaks are known or expected. Otherwise we will have to check in detail if a change is applicable into a minor or patch release or needs to be postponed until a major can be done again.

Feedback?

WIP will require the current branch to be checked out using

composer require propel/propel:"dev-... as ..."

not sure how we can access that dynamically, or if we can just copy over the existing checked out propel code into the vendor dir?

[codecov-commenter]

Codecov Report

Merging #1735 (be798df) into master (0692734) will not change coverage. The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1735   +/-   ##
=========================================
  Coverage     88.32%   88.32%           
  Complexity     7745     7745           
=========================================
  Files           263      263           
  Lines         22232    22232           
=========================================
  Hits          19637    19637           
  Misses         2595     2595           

Flag	Coverage Δ	Complexity Δ
5-max	88.32% <ø> (ø)	7745.00 <ø> (ø)
7.4	88.32% <ø> (ø)	7745.00 <ø> (ø)
agnostic	73.65% <ø> (ø)	7745.00 <ø> (ø)
mysql	70.48% <ø> (ø)	7744.00 <ø> (ø)
pgsql	70.47% <ø> (ø)	7744.00 <ø> (ø)
sqlite	68.42% <ø> (ø)	7744.00 <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 0692734...be798df. Read the comment docs.

[dereuromark]

This is not to be approved :) It is WIP and contains, as mentioned above, further work for actually doing what it should be doing.

[dereuromark]

Anyone any ideas on how we can now implement this integration testing on a large live project like this? Or should we just close? I think it would have warned us about the bc breaking effect of the one topic of beta release up front.