Skip to content

C#: Fix the unit tests for ZipSlip #1

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

Merged
merged 2 commits into from
Aug 15, 2018

Conversation

calumgrant
Copy link

I noticed that the tests has failed on your pull request, so I created a fix to save you some time.

The reason that ZipSlip.cs failed is because the QL tests run on Linux, which always uses .NET Core. So ideally, all tests need to reference assemblies from .NET Core. These are generally available but it can be a little tricky to hunt down the right one.

The reason that TaintedPath.cs failed was because the relative path or System.Web.cs has moved. This is a stub file, because that assembly isn't in .NET Core.

I also updated the .expected test output since you renamed the source file.

Copy link
Owner

@denislevin denislevin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this compiles against .NET Core now? I didn't realize this functionality is available in .NET Core

@denislevin denislevin merged commit cdc065c into denislevin:denisl/cs/ZipSlip Aug 15, 2018
@calumgrant calumgrant deleted the cs/ZipSlip branch August 15, 2018 14:05
denislevin pushed a commit that referenced this pull request Jul 22, 2019
CPP: Tests for: Better overflow detection for AssignAdd/AssignSub
denislevin pushed a commit that referenced this pull request Jul 22, 2019
JavaScript: Remove a few more configurations from AllConfigurations.qll.
denislevin pushed a commit that referenced this pull request Jul 22, 2019
C++: NonConstantFormat taint only for string types
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants