-
Notifications
You must be signed in to change notification settings - Fork 449
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
QA: Manual test and report or create test for sql injections on a local instance of the API #929
Comments
I would like to take up this issue. |
Assigning you. Good luck : ). |
@Anmollenka hey any updates? |
@vj-codes sorry for the delay.My laptop had crashed few days ago and I had given for repair.Will raise a pr within 2 3 days. |
@Anmollenka the community guidelines mention updating your progress every 3 days if it's taking long otherwise issue will be unassigned, any updates for this? |
@vj-codes as my exams are going on I am unable to work on this.It would be okay if someone else works on it.Will start contributing from april . |
@Anmollenka thanks for letting us know, I will make the issue available and if it's not claimed by anyone after your exams you can reclaim and continue also :) |
Hey, is it available? I am new to testing and would like to contribute. Thanks! |
Assigning you @saloni3487 |
Warning
This issue involves SQL injections. SQL injections should be performed on your local instance of the API and not the main API itself. If you do need to use the main API please make sure you have the necessary permission from one of the maintainers (@isabelcosta).
Is your feature request related to a problem? Please describe.
Currently there are no tests for SQL injections.
Describe the solution you'd like
Tests for Sql Injections.
Additional context
Since we aren't using raw SQL it shouldn't be a problem but I think having test would be better.
The text was updated successfully, but these errors were encountered: