Unable to release v3 due to some bugs.

[Mike214]

We’ve built a social network platform for dedicated community use. We currently have over 100 users. But we got stuck while releasing our v2. We found various bugs in our code are causing issues in the overall user experience we want to make sure that we clear these bugs before we launch our v2 for our users.

Is there a way to identify those bugs before going into test/release phase of software building?

[Dormilich]

typically you would use logging for that.

[dreamtext]

As dormilich said use logging.

But also look into test driven development. You should be able to write some tests that you can run at compile time that will help minimize bugs each time you release.

[Mike214]

We are still working on streamlining our QA process and that's why I felt a need of evaluating the project's performance even before it goes to QA. to save the deployment time and adjoining processes.

I came across an automated code review tool called Codegrip. That promises me solve this issue any thoughts?

[dreamtext]

Have not heard or used Codegrip.

You might demo it to see how much of the bugs it captures on a few releases.
It seems the code will have to uploaded and shared on their services for it to be reviewed.

How will you capture bugs that are more feature QA, where they would pass these general tests but might fail real world usage?

Maybe a combination of both manual and automated.
Have you looked into other forms of automated code reviews that don't required you to upload the company's code to another service?