-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
WIP: add new test to uncoverage SQLite3 method. #1803
Conversation
I'm not sure how this test works. |
Hello @krakjoe how are you? please, give me some example and ill fix this code! |
hello @krakjoe how are you? i'll try explain what i want to do: 2)these lines, a want this function return anything, false, exception or some error, because the param is invalid, but the same time this function return a boolean true. Do you know if is a correct ? Thanks!!! |
@krakjoe its simply for coverage, the return value will in 99% cases always be true, the only way we can trigger a warning is if libsqlite3 was compiled with their API Armor (which we do not do for the bundled libsqlite3), I did a commit related to this PR as I was reading through it but forgot to reply: @marcosptf The test seems good enough to me |
@KalleZ sorry but adding tests that are going to intermittently fail (even in a tiny minority of cases) doesn't seem sensible to me, so I won't commit this. Can't a skipif be added to detect the case where it may raise a warning and skip, if that makes sense ? |
Hello @krakjoe how are you? this --skipif-- tag is used by: and many others scripts. please, give me some example and ill fix this code! have a nice day! |
I believe we have new abilities in this area, XFAILIF, please research it and update test accordingly. |
thanks, fixing.... |
Merged 6347e25 Thanks. |
new test to sqlite3 module.