Sometimes people do not realize issues in code until they spend a lot of time running it and then it run into rare code cases where it fails on. Sometimes it is good to check those cases externally.
Here is their homepage for more info: https://www.codacy.com/ It actually rates their code on projects and also has C and cpp checks as well. It rates code by the following:
No issues = A
some issues = B
and anything more is C or lower.
Otherwise it can check things lie PEP8 things as well.
(Sadly it does not check for bugs on working code to check for things like race conditions in futures.)(And I know of some cases that using a normal for loop can sometimes exit the for loop before it is complete and do other things and then reenter the for loop instead of staying in that for loop and then exiting it when complete which is such a tricky bug to fix.)
Sometimes people do not realize issues in code until they spend a lot of time running it and then it run into rare code cases where it fails on. Sometimes it is good to check those cases externally.
Here is their homepage for more info: https://www.codacy.com/ It actually rates their code on projects and also has C and cpp checks as well. It rates code by the following: No issues = A some issues = B and anything more is C or lower.
Otherwise it can check things lie PEP8 things as well.
(Sadly it does not check for bugs on working code to check for things like race conditions in futures.) (And I know of some cases that using a normal for loop can sometimes exit the for loop before it is complete and do other things and then reenter the for loop instead of staying in that for loop and then exiting it when complete which is such a tricky bug to fix.)