Traditionally, Quality Assurance (QA) has been a very manual process. Our QA teams do an amazing job running through test plans, finding critical bugs, and logging reports. But it can be a lot of work to run through the tests again and again, dig into the errors to provide the contextual information developers need to fix bugs quickly, and prepare the reports your developers need to find and fix errors in the codebase.
We sat down with Rollbar CTO, Cory Virok, for a Q&A on how his leadership role and industry expertise helped create an enterprise solution for today’s modern software company.
What’s better than an SDK that supports iOS? One that also supports macOS! With the latest version of rollbar-ios (v1.8.1), Rollbar now supports crash monitoring for macOS. You can use Rollbar to monitor, triage, and debug crashes and errors on both iOS and macOS. What else, you ask? We’re excited about some significant improvements for both iOS and macOS. Read on for the details. Real-time crash monitoring & debugging for macOS
In this tutorial, you will be introduced to errors tracking in Angular 7 using the errorHandler class and Rollbar. This is the last part of the Angular 7 error handling series, you can refer to the first part here, and the second part here. In this series, you have been introduced earlier to handling client side errors and then HTTP errors gracefully in Angular 7 with tools like errorHandlers, Interceptors and even RxJS operators.
Does your team use Azure DevOps for tracking work? You’re going to love our latest integration if that’s the case. You can now create and resolve Work Items in Azure DevOps directly from Rollbar, making error monitoring and debugging even faster. This is the latest addition to our toolkit for the Microsoft ecosystem (read about our Azure Active Directory integration). It reinforces our mission to help software developers build software quickly and painlessly.
Tools like Rollbar have changed the way development teams are recording and managing their exceptions. What used to be a very personal developer-by-developer activity can now be a team-wide tool for greater transparency, and increased application quality. But many still treat exception monitoring as a developer activity, and they are not leveraging its benefits across all environments, from development to stage and integration, to systems testing and production.
As Java has evolved over the years, multiple attempts have been made to simplify development for various use cases. From official standards like Java Enterprise Edition, to community-driven frameworks, Java is continuing to prove itself to be adaptable and viable. Our top list is based on usage from Hotframework.com's Java ranking and several other sources including blog posts and GitHub download numbers.
In production, the most important advantage of using a build tool like webpack is a smaller size and thus improved overall application performance. Although beneficial for our users, the bundled and minified code is harder to debug for developers as the code they have written doesn't map 1:1 to error stack traces. Multiple tools for minifying, bundling and transpiring JavaScript modules can generate source maps along with the resulting code.
Continuous delivery (CD) helps reduce the cost, time and risk of delivering changes by allowing for fast incremental updates to applications in production. However, it’s essential to monitor your application after each deployment. You need to be notified immediately if something is wrong or users are having a poor experience. Rollbar is a leading solution for error monitoring in the software development lifecycle. It alerts you when new errors occur after a deployment.
Imagine that you are developing an application and there's an error in the code. When you release it to production, this error causes hundreds of thousands of crashes. In this case, a logging tool would list all the crashes but an error monitoring tool, like Rollbar, would attempt to group the crashes together. Now you would receive just one notification about an error that crashed hundreds of thousands of times instead of many notifications about different crashes.
