-
Notifications
You must be signed in to change notification settings - Fork 94
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
Do not stop if one unit test fails #14
Comments
hey is this issue still exists? if so can i work on this? a try catch blocks? or should i use unittest to keep consistency? asking this as i see there is |
Oh yes, the issue still exist. Feel free to work on it. I was actually referring to this one: https://github.com/google/gcp_scanner/blob/main/src/gcp_scanner/test_unit.py. It fails as soon as the first assert is not satisfied. I'd use |
oo ok gotcha |
@Pavan-Nambi Can I pick this up? |
hey @jatinagwal yeah feel free to do so , i got into some work so wasn't able to do , appologies for delay |
I am also interested in this issue if it's open. |
@mshudrak I think its best practice to write single assert per test function. If you agree, I can take on the issue and refactor the tests. |
Signed-off-by: Sudipto Baral <sudiptobaral.me@gmail.com>
Signed-off-by: Sudipto Baral <sudiptobaral.me@gmail.com>
Signed-off-by: Sudipto Baral <sudiptobaral.me@gmail.com>
Signed-off-by: Sudipto Baral <sudiptobaral.me@gmail.com>
Currently, our unit test process stops as soon as one test fails thereby making it hard to evaluate what else breaking without actually fixing the error and relaunching test again. We need to first run all tests and then print summary of failed functions.
The text was updated successfully, but these errors were encountered: