These are chat archives for Microsoft/CodeContracts
How does the testing situation look?
All unit tests are passing (for ccrewrite). All changes are reviewed by original author (by Mike). I'll test on our own codebase (we're using code contracts very extensively: few hundreds KLOC of code with a whole lot of contracts).
Other than that, I don't know what we can do.
As a bottom line, my idea was to use Mike for this release, because I would like to publish this new release to the old Code Contracts web-site (https://visualstudiogallery.msdn.microsoft.com/1ec7db13-3363-46c9-851f-1ce455f66970).
Now that this is a community project, we should also share the preview with all participants in the project. We can attach the installer to the GitHub Releases page for it
I'm ok with that.
How extensive are the unit tests? I haven't run coverage analysis on them.
They're limited. And believe me the code is super complicated, so code coverage doesn't mean anything here. And again, because the code is so complicated the only reasonable approach for short term - is to get a feedback from the original authors. What to do next? I'm not sure, because without Francesco it is almost impossible to add any significant changes to the CCCheck. CCRewrite is also super complicated (because it is based on IL rewriting) but code coverage is better.
I'm totally agree about CI and all this stuff. But as I mentioned, I fixed only ccrewrite tests, I don't know about ccchecks (they could be broken). And to fix ccrewrite tests I changed some of the ccrewriter logic (with confirmation from Mike and Francesco). I.e. we could have some issues for this automation. As you suggested we can disable some tests, but in this case our (small) code coverage would be even smaller and we still would not have a confidence that there is no regression.
So we would have kind of chicken and egg problem here: we don't have tests to check regression, but to fix tests we need to fix production code.
Long story short: I would love to have CI but not sure that it is possible to have it ASAP, just because it could take a while to get there.