Ten years ago I saw a Selenium test that could click on a capital "I" that was one pixel wide. I was not capable of clicking on it myself. Around that time, a lot of people began using phrases like "End to end is further than you think." Simulators and emulators, after all, could not simulate heat, poor memory management, low power, and other problems. Then again, that was ten years ago.
Last week was kind of crazy. Apple announced the public release of iOS14 on the day before triggering a major Twitter-meltdown among developers. Thanks to the quick response of our team, just under 20 hours later we were able to release the new Xcode 12 stack on Bitrise.
By combining custom errors, named functions and Bugfender, you can create a robust error-handling process that allows you to immediately identify the defects of your JavaScript apps. Unhandled JavaScript errors will stop the execution of your script, leaving the application in an undesired state – or, even worse, in an unknown state. So you need a robust error-handling process to avoid unknown errors in your apps. But, why are errors thrown anyway?
Kicking off our Ask Me Anything series, Bitrise Sales Engineers Damien Murphy and Tamas Bazsonyi answered questions about new features, roadmap plans, and shared some of the tricks&tips on using Bitrise like a natural.
