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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Nodejs] Update iast stack trace tests #3746
[Nodejs] Update iast stack trace tests #3746
Changes from all commits
8d47cbe
a926b73
47906a6
55253da
e6f903f
b3c0dc7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @IlyasShabi , @uurien, @iunanua
For later PR/reviews => this change modifies a test. I'm quite confident that it'll be ok because the
integration
scenario is very close to the default scenario. But rule of thumb, it's better to not use a prefix ([nodejs]
) in the title in that use case, to be 100% sure we don't break anything. Otherwise, we'll face complaint in apm-shared-testing 😉There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @cbeauchesne the
nosql_mongodb_injection
stack trace test was not working due to this missing scenario, which is why we introduced this line.As you can see in the PR history, I ran tests for all languages to ensure nothing was broken, and then I switched to
[Nodejs]
for minor changes, like updatingdd-trace-js
versionsThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice :) I didn't noticed this succesion of event 👍
AGTM, as long as no issue is introduced 😉