JS: show test changes after #15823 #15883
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a journey for me into better understanding the JS CodeQL analysis, by trying to write tests to show the effect of #15823. I've written some tests that initially fail on commit 245cd5c (parent of PR merge commit), and then tested them again on 7c35309 (PR merge commit)
I was able to highlight the effect of the Detect more FunctionStyleClasses commit, see the change in
javascript/ql/test/ApiGraphs/classes/VerifyAssertions.expected
.I had expected that the step defined here
codeql/javascript/ql/lib/semmle/javascript/dataflow/internal/StepSummary.qll
Lines 120 to 121 in 13e3a51
obj_
type-tracking test to pass after the changes in the PR, but that was not the case.So I wasn't able to write a test that highlights the impact of the change in f5d014b, even though I can see the change in
impliedReceiverStep
when quick-eval'ing locally. @asgerf can you highlight the end-result impact of that commit? 😕