Make integration test pass

[withsecureopensource]

Make integration test pass

[matveypashkovskiy]

Should it somehow parse the diff data to find new def declarations with +-sign? This would probably also cover renames too but that's one way I thought of. Or should it somehow use the line numbers inside the @@ symbols to determine that new lines are added to the bottom of the file?


What if we check coverage for new lines? If there is no information about those lines run all tests for that file?

Integration test expects the newly added tests to be found in the working directory changes. If this is added, when would be the time to update the database (add the test)? If a test is discovered in the working directory changes but never added to the database before the branch test selection, the test is always found in the working directory changes and the script never progresses to look at the committed changes.


Can we always check uncommitted changes and results of branch-to-master comparison? And basing on that two datasets decide what to do next.