Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Affected strategy doesn't pick up changes made in the other module #43
This could be related to the fact that we use
Code modified in one module is not treated as affecting tests from the other one.
Generally speaking, it is a fair assumption that tests and code under test belong to the same module, but as soon as we cross the boundaries of unit testing this might not hold true anymore.
When changing source in one module, tests which are related to it, but belong to another module, should be detected and run if the whole project is built.
Steps To Reproduce