From the knowledge I have acquired while doing automation with other tools, I want to ask about specifics of doing that in Selenium (with Java). Questions:
I remember watching a video on Junit where all the assert methods are wrapped up in a try block and an additional library is imported to make sure that a test fails, if an assert fails. How common is that approach?
Contrary to above, some say that you should never put assert methods in a try block. If you do that, running a java file will pass, even if an assert fails. Is doing this way also common?
If you have many tests to run, is it common to sort returns of assert methods in an excel file and later run only those tests, where asserts return false?
If you do continuous integration, it is important, from the way I understand, for a run to fail, if an assert method returns false. Otherwise, unfixed bugs will be deployed into production. Am I right and if so, how do you assure that that happens?