Skip to content

Commit 4ec527a

Browse files
committed
Ruby: Explain difference between flow tests
The type-tracking flow tests document the difference in sensitivity between type-tracking and dataflow, so failures in that test are expected.
1 parent 6e8446b commit 4ec527a

File tree

2 files changed

+10
-0
lines changed

2 files changed

+10
-0
lines changed
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,6 @@
1+
// This test flags any difference in flow between the type-tracking and dataflow
2+
// libraries. New results in this query do not necessarily indicate a problem,
3+
// only that type-tracking cannot follow the flow in your test. If the dataflow
4+
// test (`array-flow.ql`) shows no failures, then that may be sufficient
5+
// (depending on your use case).
16
import TestUtilities.InlineTypeTrackingFlowTest
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,6 @@
1+
// This test flags any difference in flow between the type-tracking and dataflow
2+
// libraries. New results in this query do not necessarily indicate a problem,
3+
// only that type-tracking cannot follow the flow in your test. If the dataflow
4+
// test (`hash-flow.ql`) shows no failures, then that may be sufficient
5+
// (depending on your use case).
16
import TestUtilities.InlineTypeTrackingFlowTest

0 commit comments

Comments
 (0)