Hi.
Is it a technical reason (vs design decision?) for why tests are considered "impacted" even though the change only involves changing of code comments?
(The scenario is when I update test comments the tests are re-run when having "IsImpacted" engine mode condition. Ideally I would expect only changed covered code lines to trigger the "IsImpacted" condition).
Thanks.
Daily Usage Issues
Tests impacted when only editing test comment?
Started by GreenMoose on 5,541 views
Remco NCrunch Developer
#7999
15 Nov 2015 06:06 UTC
Hi,
Yes. NCrunch's impact detection is currently very rudimentary, it works above the compiler step and does not consider the IL.
This has advantages in terms of simplicity and performance, but it isn't very accurate. Simply changing the code will trigger tests to be impacted, regardless of whether such a change actually impacts the compiled code.
IL-Level impact detection is expected as a future feature.
Yes. NCrunch's impact detection is currently very rudimentary, it works above the compiler step and does not consider the IL.
This has advantages in terms of simplicity and performance, but it isn't very accurate. Simply changing the code will trigger tests to be impacted, regardless of whether such a change actually impacts the compiled code.
IL-Level impact detection is expected as a future feature.
Post a reply
Log in to reply.