Use coverage to detect test-production classes dependencies
Issue Overview
Currently affected strategy just works with black box testing(or white ones if ShrinkWrap or VertX runner is used). In #214 we mention to create a file where developer can set the relationship between test and production code under test. We could automate this by using coverage information.
Currently affected strategy just works with black box testing(or white ones if ShrinkWrap or VertX runner is used).
it is the other way around - currently, it works with white box tests, not black box, right?
Yes it does not work with black box if vertx or shrinkwrap not used
El 12 oct. 2017 4:26 p. m., "Matous Jobanek" [email protected] escribió:
Currently affected strategy just works with black box testing(or white ones if ShrinkWrap or VertX runner is used).
it is the other way around - currently, it works with white box tests, not black box, right?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/arquillian/smart-testing/issues/215#issuecomment-336153885, or mute the thread https://github.com/notifications/unsubscribe-auth/ABcmYejvrVaXBWHPCQcT-iyDAQ_PXOUDks5sriGLgaJpZM4PwkdJ .
Related to https://github.com/arquillian/smart-testing/issues/264