MuukTest, an AI test automation platform, is excited to announce the launch of TestXplainer, a generative AI tool that empowers everyone involved in QA by translating data into clear and simple test strategy information that is accessible to all.

Redefining AI Software Testing: MuukTest Unveils TestXplainer

The Software Testing and Quality Assurance course is a vital component of modern software development, aimed at ensuring that software applications meet the highest standards of reliability ...

Software Testing and Quality Assurance course | H2kinfosys

Note: At Cybernews, we regularly test and research antivirus software to update this list with products that are of the highest quality. Choosing the best antivirus might seem challenging at first. There are so many options offering a variety of different ...

Best antivirus software for 2023

For instance, incorporating quality assurance processes at each phase of the software development lifecycle reduces the rate of defects at the later stages of software development. This eventually reduces the need for rework and minimizes the development ...

Beyond Billboards: Why Quality Software Speaks For Itself

But how do you know you’re getting the sound quality you deserve? In this article, we’re going over how to perform a successful headphone test, uncovering the ultimate guide to evaluating ...

The Ultimate Headphone Test for Sound Quality

It helps managers prioritize projects among a long list of goals. Portfolio management software aids managers in keeping a high-level view of which projects are meeting the needs of the ...

Best Project Portfolio Management Software (2023)

Our client, a medium sized IT company based in Somerset specialises in Business Intelligence, SAP software, Enterprise Performance Management, and related planning as well as reporting systems. We currently are searching for an ambitious and dynamic ...

Business Analyst (SAP BI and Analytics) (C955) – Western Cape Cape Town

Apple said that the testing protocol used by L’Agence Nationale des Frequences did not take this feature into account. The company issued a software update that will become broadly available to ...

Apple updates iPhone 12 software to address France’s radiation testing

Get the most recent info and news about bugsnag on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

bugsnag

How NetEngine Tracks Critical Bugs Using BugSnag

Yelp's Mobile App Stability Soars to 99.98% with BugSnag

How Shopify Uses BugSnag to Service Over 377,000 Online Stores

: NetEngine’s business is based on providing high-quality stable software to its clients, however, developers lost visibility into software when it was delivered to customers and deployed to production. The team was only alerted of errors from customer complaints, leading to an unpleasant experience for developers and customers. Challenge : Using Bugsnag, NetEngine has visibility into production errors and can often preemptively fix errors before customers are aware of them. Bugsnag allowed NetEngine to fundamentally change their business model to offer an ongoing contract with clients for software management, and provide an overall better customer experience. Results NetEngine’s business depends on creating high-quality software, but without error monitoring, critical bugs went unnoticed. NetEngine creates web and mobile products for a range of industries, such as travel, health, recruitment, local government, and non-profit. They create Ruby on Rails and JavaScript web and mobile products using proven lean and agile methodologies. NetEngine’s business depends on developing great software solutions for their clients, making it imperative to deliver stable, high-quality software. However, the engineering team had no error monitoring tool in place, which meant bugs in production went unnoticed until a customer complained. “When a customer finds a bug, they are irritated as is, and they obviously do not want to get invoiced for buggy software,” mentions Bruce Stronge, cofounder and CEO of NetEngine. After a disgruntled customer notified the team of an error, a developer had to try to replicate it, digging through log files, or even contacting the customer to try to piece together what occurred. “Troubleshooting bugs with this process would take an entire day for 2 or 3 of our developers,” states Stronge. “In addition, we would have the customer calling every hour to know if the issue was fixed. All in all, this posed a lot of stress and dissatisfaction for all parties involved, and it was definitely not the type of experience we want to deliver.” Improving customer relationships with proactive error monitoring NetEngine sought out an error monitoring tool that would let their developers proactively address bugs, helping them deliver quality software in a timely manner, and therefore create long-lasting relationships with their clients. NetEngine chose Bugsnag as their error monitoring tool because of the ease of implementation and use. “Because Bugsnag is so affordable and easy to set up, we can use it for every project and not just the large, high-budget ones. The moment our customers have a pilot, they have error monitoring for it.” — Bruce Stronge, Cofounder and CEO Thanks to Bugsnag, NetEngine’s developers save valuable time when addressing errors. “We can fix bugs in 30 minutes instead of 2 days,” comments Stronge. “Our customers hardly see any bugs, because we fix them right away.” Using Slack and TriggerApp integrations to improve efficiency Bugsnag’s Slack integration is another highly used feature at NetEngine. It lets engineers know immediately when an error occurs, and the impact of it. “Each of our 25 developers now saves 10 minutes every two hours, because they don’t have to search for errors and then alert the rest of the team. We get automatically notified when errors occur,” mentions Stronge. “Another powerful integration is with our project management tool TriggerApp, where tasks are now automatically created and assigned from Bugsnag - a huge efficiency creator”. Bugsnag has not only allowed NetEngine to save valuable time when troubleshooting exceptions, but they are also able to maintain an ongoing contract with their clients, which is seldom heard of for project-based consulting companies. “We are easily able to sell the benefits of Bugsnag to our clients,” says Stronge. “By having a maintenance contract with our customers, we maintain ownership of a product, and can more easily find and fix any issues that arise.”

Cómo NetEngine realiza un seguimiento de los errores críticos mediante BugSnag

Comment NetEngine suit les bogues critiques à l'aide de BugSnag

NetEngine BugSnag का उपयोग करके महत्वपूर्ण बग्स को कैसे ट्रैक करता है

NetEngine が BugSnag を使用して重大なバグを追跡する方法

Como o NetEngine rastreia bugs críticos usando o BugSnag

Cách NetEngine theo dõi các lỗi nghiêm trọng bằng BugSnag

NetEngine 如何使用 BugSnag 跟踪关键错误

: Yelp recognized that its previous crash reporting tool provided inadequate search functionality for developers and caused a slow cold start Android app launch for users. Challenge : Yelp has achieved a 99.98% stability target using Bugsnag to improve its app stability. As a result, Yelp fulfills its promise of a dependable and fast user experience, which is reflected in its impressive Google Play ratings. Results Yelp strives to deliver crash-free mobile experiences Yelp, a popular local-search platform that connects millions of consumers with great local businesses, is tied directly to the consistent delivery of a stable and expeditious mobile app experience. To live up to expectations, information must be instantaneously available to users in their moment of need, which means app crashes are completely unacceptable. As Antonio Niñirola, Yelp’s Core Android Engineering Manager, explains, “If an app crashes twice, I’m going to uninstall it because it’s a bad app. I don’t care which app it is. Yelp aims to never be in that position.” Visibility into crashes helps maintain strong user experiences As the Android team has grown at Yelp so has the need for a stability monitoring solution. While the original team was small and able to work together to figure out why a crash occurred, today’s team and development process have grown to approximately 50 contributors for every weekly release. Stability and crash monitoring are critical for managing this speedy release process. While Yelp started with an internally developed tool, they quickly realized it was difficult to maintain and wasn’t worth the investment. They switched to Crashlytics but encountered challenges which led them to start exploring other tools. “We like to have as low a cold start as possible when the user starts to use the app for the first time,” according to Antonio. Bugsnag delivers results through the stability score, search, and integrations Yelp’s Android team was the first team within Yelp to select Bugsnag as its stability monitoring solution after evaluating it against Crashlytics. The iOS and web teams have subsequently adopted Bugsnag after hearing about the numerous benefits. The Bugsnag Releases dashboard is used to see adoption numbers and the stability score for each release which gives a clear understanding of its health. Since the Android team does an alpha release every day and a beta release every week, the ease of identifying problematic releases is key to their success. “Bugsnag makes it easy to receive an alert whenever something goes wrong, and is extremely quick. Alerts allow triage to occur without delay, and Bugsnag has no negative impact on app starts. Bugsnag’s error libraries are completely open source, which allows us to actually look at the code.” — Antonio Niñirola, Engineering Manager Antonio also finds that the strong search functionality further accelerates the debugging process. When a bug is assigned, developers can easily find the information they need and Bugsnag provides more intelligent error grouping than competitor products. With Bugsnag’s integrations to systems like and Splunk, Yelp benefits from seamless information sharing across systems. For example, release information from Bugsnag is pulled into Splunk and merged with other internal metrics and data sources in order to make data-driven decisions that impact the broader business. Slack Antonio and his team appreciate the strong feedback loop to Bugsnag. “Over the years, we’ve communicated a lot with the Bugsnag team, and a lot of our feedback has been addressed,” Antonio states. Yelp reduces the number of crashes through preemptive detection Bugsnag is now part of Yelp’s release management process, and the stability score is the main metric used to determine success in weekly releases and staged rollouts in Google Play. As a result, Yelp updated their stability target from 99.7% to 99.98%. They also reduced their APK size by approximately 50 percent, thanks in part to Bugsnag’s small library size. Since adopting Bugsnag, the Android team has noticed a decrease in the number of crashes reported by their beta group in Play. Yelp attributes part of their release process improvements to the implementation of Bugsnag and their ability to find crashes before they release. Google “I would say that crash reporting is one of the main things you should have in your app. It’s super important to have visibility, especially within a large organization like Yelp. Detection is 100% faster when you have crash reporting.” — Antonio Niñirola, Engineering Manager Also published . here

La estabilidad de la aplicación móvil de Yelp se eleva al 99,98 % con BugSnag

La stabilité de l'application mobile de Yelp monte à 99,98 % avec BugSnag

बगस्नैग के साथ येल्प के मोबाइल ऐप की स्थिरता 99.98% तक बढ़ गई है

Yelp のモバイル アプリの安定性が BugSnag で 99.98% に上昇

A estabilidade do aplicativo móvel do Yelp sobe para 99,98% com o BugSnag

Độ ổn định của ứng dụng di động của Yelp tăng vọt lên 99,98% với BugSnag

Yelp 的移动应用程序稳定性借助 BugSnag 飙升至 99.98%

: Reliability is Shopify’s top priority for its 300 thousand-plus daily users. Without the ability to gauge the impact of errors, Shopify engineers had limited visibility into user experience, and oftentimes, customers contacted them with problems before errors were discovered. Challenge : Using Bugsnag, Shopify engineers are aware of errors significantly faster, can more easily replicate errors, and can proactively see the effects of their code. Trend analysis helps engineers understand common causes of errors and mitigate future problems. Results Before error monitoring, ensuring reliability for Shopify’s worldwide customer base was tedious, time-consuming, and inefficient. Shopify develops e-commerce software for more than 377,500 online stores and retail point-of-sale systems around the world. For Shopify’s engineering team, the top priority is to maintain reliability for each customer worldwide. However, that process used to be very time consuming and tedious for Shopify’s software engineers. “Troubleshooting used to be slow and unpleasant, requiring us to invest a lot of time digging through logs and piecing together information from multiple sources,” states Blake Mesdag, Sr. Developer for Shopify’s CI Infrastructure team. Trend analysis is another great way to mitigate potential exceptions, but before error monitoring was implemented, it was difficult to build a complete picture of errors over time. Without spike notifications, alerts that indicate a sudden increase in the occurrence of an error, bugs would escalate and affect customers, requiring them to reach out to Shopify so they could be fixed. Preempting Support Calls With Increased Visibility Into Errors It soon became apparent that a more proactive way of addressing errors had to be implemented for all of Shopify’s development process. “Without error monitoring, you’re flying blind - there’s almost no point if you can’t see what you’re doing right and wrong, and you can’t make any informed decisions,” says Mesdag. After considering several options, Shopify chose Bugsnag for automatic error monitoring of their entire tech stack. Shopify’s developers, across 20-30 teams, can now proactively see the effects of their code and identify and troubleshoot errors before they impact merchants. “Overall, Bugsnag has helped me become more confident in the code I ship, which in turn helps me ship faster” — Blake Mesdag, Sr. Developer Before Bugsnag, Shopify software engineers could not proactively see what errors were occurring and would have to wait for customers to reach out with problems. They would then have to dig through logs to find an exception ID, and then use that to find it in the exception tracker. “Bugsnag surfaces all of this information in one place, and it tells us exactly what caused the error,” states Mesdag. “There is a lot less search involved with Bugsnag, and the overall process of troubleshooting bugs is significantly more pleasant.” Using Trend Analysis to Mitigate Future Errors With Bugsnag, Shopify developers can also analyze trends on exceptions. This helps them understand common factors that cause failures so they can take a proactive approach to mitigate these in the future. Trend analysis is powerful for the infrastructure team to diagnose if specific machines are causing more issues than others. In addition, by having spike notifications, it becomes much easier to pinpoint errors that are quickly escalating, prioritize them, and get them fixed much faster.

Cómo Shopify usa BugSnag para dar servicio a más de 377 000 tiendas en línea

Comment Shopify utilise BugSnag pour desservir plus de 377 000 boutiques en ligne

शॉपिफाई कैसे 377,000 से अधिक ऑनलाइन स्टोरों को सेवा प्रदान करने के लिए बगस्नैग का उपयोग करता है

Shopify が BugSnag を使用して 377,000 以上のオンライン ストアにサービスを提供する方法

Como a Shopify usa o BugSnag para atender mais de 377.000 lojas online

Cách Shopify sử dụng BugSnag để phục vụ hơn 377.000 cửa hàng trực tuyến

Shopify 如何使用 BugSnag 为超过 377,000 家在线商店提供服务

: As Namely’s HR offerings and engineering team scaled, it became evident they needed to standardize how troubleshooting software bugs was done. Until then, each engineering team had its own process, and the previous tool they used did not support many of the coding languages used at Namely. Challenge As of early 2017, all of Namely’s engineering teams use Bugsnag to troubleshoot errors. This has allowed them to unlock several benefits, such as becoming aware of bugs and understanding the root cause 50% faster, and improving their customer’s experience by continuously keeping application stability as top of mind. Results: Namely was looking to standardize the way they addressed errors across all engineering teams in order to remove complexities and save valuable time. Namely is an all-in-one human resources platform for businesses of all types. As the number of Namely’s HR products increased, so did the number of engineering teams and the different coding languages they used. “Once you move away from a monolith and into a microservices framework you add significantly more complexity to the process,” states Teresa Dietrich, CTO of Namely. “We wanted to remove that complexity by standardizing the way we did error monitoring across all of our teams and languages.” Namely’s previous error monitoring tool was mainly built for , and did not support other key languages like Core, which is used for Namely’s core product, Payroll. The lack of language support meant many teams did not have an error monitoring tool in place, and relied on customers flagging errors via support tickets. On the other hand, those who did use the previous tool had limited ability to track errors, and information was scattered throughout multiple applications. Ruby .NET One error monitoring platform for all frameworks As of Q1 2017, all of Namely’s projects and engineering teams use Bugsnag for error monitoring. Since then, they have reaped countless benefits. Aside from being able to use Bugsnag for all applications regardless of language, they also now have support for SAML and SSO, two very important protocols given the amount of personal information that Namely handles for their customers. Also, unlike their previous tool, engineers can use precise filters on each project’s error data, allowing them to sift through the noise and only get notified of bugs that matter. “We get information about a bug at least 50% faster.” In general, Bugsnag has allowed Namely to monitor for errors more efficiently and troubleshoot bugs significantly faster across all engineering teams. Identifying and understanding an error’s root cause is also faster with Bugsnag. “We are no longer going into three different systems to get information about a bug,” says Robert Ross, Core Services Software Engineer. “We can skip logs and NewRelic and get everything in one place.” Improving the customer experience with quality software In addition to improving how troubleshooting is done, Bugsnag has allowed Namely to further focus on their customer’s experience. Engineers are not only shipping products with even higher stability than before, but they can also fix issues and respond to customers much faster. “I’ve heard several of our engineers recommend Bugsnag to others,” says Dietrich. “That on its own is a testament of how much value they see in Bugsnag. It significantly alleviates the pain of troubleshooting errors.” “We are working on more bugs than before and are able to identify them much faster.” — Teresa Dietrich, CTO Also published . here This story was distributed as a release by Bugsnag under HackerNoon’s Brand As An Author Program. Learn more about the program here: https://business.hackernoon.com/brand-as-author

How Bugsnag Empowers Namely's Engineering Team with Error Troubleshooting

: Gusto’s business is designed around empowering a better life for all employees through their work, but existing bug-fixing processes didn’t fit this goal. The process of finding and fixing bugs was complicated, tedious, inefficient, and all-around unpleasant for Gusto engineers. Challenge Gusto redesigned its bug-fixing process around the idea of code ownership. Using , engineers have visibility to errors that occurred in the code they wrote, clear indicators for the impact of each error, and the resources needed to diagnose and resolve errors quickly. Results: Bugsnag As Gusto scaled, their process for identifying and fixing errors became a burden on the engineering team Gusto is a comprehensive HR, payroll, and benefits platform for small and medium businesses. Gusto has an extensive human resources platform and more than 90 developers who diligently work on creating and maintaining its multiple applications, like payroll, health benefits, payments, risk checks, and others. As each of Gusto’s applications scaled and the number of customers grew, their engineering teams identified that troubleshooting bugs was becoming a very tedious and inefficient process for the developer assigned weekly to that task, whom they call the Viking Master. The Viking Master would halt any other priorities and solely focus on identifying and fixing bugs. Given how much code was being pushed to production, there was a lot of noise generated when it came to error notifications. Many times, the errors the Viking Master was addressing were lines of code they hadn’t written, making it even more complicated when replicating and fixing errors. The Viking Master had to spend countless hours figuring out which errors to address first, digging through logs, and reaching out to other engineers to get the full context, just in time for a new Viking Master to start from square one the following week. Creating ownership with increased visibility into errors Eddie Kim, CTO and co-founder of Gusto, knew this was not the kind of experience he wanted for Gusto’s more than 90 talented developers. To better match their company’s value of empowering people to do their best work, Gusto sought to improve the necessary task of troubleshooting errors and make it a much more enjoyable and less time-consuming process. “Whenever an error occurs, each application team gets immediately notified via Slack, where we show pertinent information about the exception and which developer committed the code.” -Eddie Kim, CTO and cofounder Reducing support tickets with streamlined troubleshooting workflow Another efficiency created by the Developer Experience team was using Bugsnag for workflow purposes. Once an error is identified, it is useful for the team to know which errors are being worked on and by whom. This ensures that no important issues fall through the cracks and that there are clear next steps as to who should be fixing what bugs. Even though the Developer Experience team is continuing to roll out more efficiencies to the error troubleshooting process, Bugsnag has already allowed them to realize some initial benefits. Mean time to resolution has decreased and all engineering teams can now enjoy smoother deploys that allow them to address errors before they escalate. “Bugsnag is a central tool that enables us to create ownership mentality for all software engineers.” -Eddie Kim, CTO and cofounder By enabling developers to more easily identify and address errors, Gusto can quickly iterate and improve their software’s performance. This leads to more robust and faster background job processing systems, such as the amount of time it takes for their customers to run payroll or file taxes. As a result, Gusto offers a better customer experience leading to fewer support tickets and increased customer satisfaction. Also published here.

How Gusto Makes Bug Fixing Enjoyable With Bugsnag

Hello, and welcome to part two of the Bugsnag Beginners Series! We will cover the error details page and how it can be used to maximize error debugging in your Bugsnag Dashboard. We’ll start by going over how error details heading information is organized, followed by what different pivots mean, how the status box works, where to find diagnostic data, and lastly how to create custom filters using your error’s metadata. Let’s start by clicking into an error from the Error Inbox, bringing us to the error details page. Error Details Heading An error’s heading information is a great place to start the debugging process. At the top of the heading is the error class, which will appear alongside the blame frame pulled from the error’s stack trace. On the line below is the error message that was given by the exception when it occurred. The bottom two lines display general information about the severity and frequency of the error, as well as the grouping logic that was applied to that particular class of errors. : Error details data will vary by platform. Note Pivots Transitioning to the next topic, let’s discuss the different list views available within a group of errors, which are known as pivots. By default, the error details page displays a class of error events based on how recently they occurred within the app; however, by selecting different pivots at the top of the page, a variety of segmented errors can be explored. Aside from the aforementioned event pivot, the segmented list views are as follows: users impacted, release stages the error was seen in, which release version the errors occurred in, features flagged within the error, and device details such as OS and model. Custom pivots also can be created for further segmentation, such as shutter speed, focal length, or VIP customers impacted, as seen below in our camera app. Status Box The status box seen on the left-hand side of the error details page contains three useful sections. The first at the very top is specifically designed for quick triage by assigning various errors a workflow status. For more on workflow statuses, check out . The next section in the status box is the histogram of the error class, labeled as the Trend. This displays the app health in relation to that error class within the currently selected time period, displaying up to 60 days of historical data. The final section in the status box is the average device state. Here, device-specific information –such as foreground duration, memory states, and whether the device was jailbroken – can be found. Part One of the Bugsnag Beginner Series Note: Average device state will only appear for mobile app projects. Diagnostic Data By clicking into the error, diagnostic data will be displayed to help better understand what steps the user took before the error occurred. The first key diagnostic that appears is the full stack trace, as well as an option to view the raw data and the threads. Next to the stack trace are the breadcrumbs, where the user clicks and screen views can be seen. Going further right, app and device state is displayed to provide device specific information that may have caused the error. Lastly, user and feature flags can be seen if previously configured, which add an extra level of granularity to the debugging process. Custom Filters From the diagnostic data display, custom filters can be created by clicking the index button found to the left of any of the metadata. Custom filters will be displayed under the Summaries box found to the bottom left of the page, and as queryable custom attributes within the Error Inbox. By default,10 custom filters can exist within a Dashboard – so create with care. If a custom filter was added by mistake, it can be deleted from Project Settings by clicking Custom Filters. We look forward to seeing you In part three of this series, where we’ll cover the Releases page and the Stability Center. Also published . here

Bugsnag Beginners Series: Part 2 - Error Details

So, whether you’re logging into the Bugsnag Dashboard for the first time or have already created several projects, this series will help you develop a strong foundation for using Bugsnag efficiently and effectively. Let’s kick things off by talking about one of the essential pages in Bugsnag, the Bugsnag Inbox. This page houses all of an app’s crash data and can be used to visualize overall app health within a customizable timeline. The grouping logic built into Bugsnag uses the underlying root cause of a crash to group exceptions as unique events. This helps minimize noise, as well as identify the most relevant crash data in the Inbox. Bugsnag displays each grouped crash with the error headline, as well as the top stack frame where the crash occurred in the app. Below the headline is the message generated with the crash, as well as when the error was last seen and first introduced. If any users within the Bugsnag project commented on the error or were assigned ownership of the bug, that can be found next to the timestamp. 1. Error headline 2. Error message 3. Last time error was seen; First introduced 4. Error comments 5. Error assignee Error Details Moving onto the right side of the Inbox, here, the crash count of each corresponding error can be found, as well as how many users it has impacted. Clicking these parameters will sort them by total count, starting from largest to smallest. Further right is the trend bar corresponding to each error’s impact within the Inbox’s current time range setting. Adjusting the Inbox’s time range can provide insight into up to two months of historical data. Next to the trend bar is the release stage that the error occurred in—Bugsnag will display both staging and production builds if the error was seen in both. Lastly, the severity of the error is reflected furthest to the right of the Inbox. Unhandled exceptions are, by default, given an “error” level of severity, and handled exceptions are marked as a “warning.” 1. Error count  2. Trend bar  3. Release stage  4. Severity level Error Triage Lastly, looking to the left side of the Inbox, errors can be assigned to various work status bins to assist triage. When an error’s status changes, it’s placed in the corresponding status bin. For example, opening an errors status assignment box by clicking the checkmark and then marking the error as fixed will move it from the “Open” status bin to the “Fixed” bin. Using this workflow will allow team members to know that the error has been actioned, as well as keep the status bins tidy. Errors can also be assigned to various team members using an error “Assigned” status or via an issue tracker integration such as Jira. Low-priority or noisy errors can be marked as “Snoozed” until they pass a customizable threshold. Lastly, for errors that don’t need to be actioned, marking them as “Ignored” will prevent them from sending notifications. Errors can also be discarded or deleted, removing an instance of the error just once or permanently, depending on the respective action. Status bins  2. Status assignment box That concludes the overview of the Bugsnag Error Inbox, as well as part one of the Bugsnag Beginners Series. Please stay tuned for the next topic, which will dive deeply into the Error Details page. See you then!

Bugsnag Beginners' Series: Part 1 - Error Inbox

Bugsnag Beginners Series Parte 1 - Bandeja de entrada de errores

Bugsnag Beginners Series Partie 1 - Boîte de réception d'erreurs

Bugsnag शुरुआती श्रृंखला भाग 1 - त्रुटि इनबॉक्स

Bugsnag ビギナー シリーズ パート 1 - エラー インボックス

Bugsnag Beginners Series Parte 1 - Caixa de entrada de erros

Sê-ri dành cho người mới bắt đầu Bugsnag Phần 1 - Hộp thư báo lỗi

Bugsnag 初学者系列第 1 部分 - 错误收件箱

As Eventbrite neared the release of their rewritten platform in React.js, they knew observability on the frontend was a problem they needed to solve. If they were going to release a dynamic, JavaScript application, they would need visibility into their product. Their homegrown solution sent errors to Splunk, but there was no clarity around which errors were problematic. CHALLENGE: Eventbrite has now implemented Bugsnag in their development and release process which has given them peace of mind. They know any bugs will be detected before they impact their entire user base. Eventbrite has also become more agile since they can release features to a subset of users, monitor incoming errors, and decide when to rollout platform wide, knowing they will be alerted swiftly of issues. RESULTS: Growth Goals and an Innovating Product Highlighted the Need for Visibility into Errors Eventbrite is an online events platform that helps organizers build, manage, and grow their events. Their software provides end-to-end online event logistics, and enables organizers to get up and running smoothly and quickly, whether they are hosting intimate gatherings or complex, large scale events. As Eventbrite solidified its platform for event organizers, they sought to grow their user base of attendees to become the destination for finding things to do. They also decided to move away from being a monolithic platform and break up their product functionality. This would allow them to offer certain services to event organizers who may not need their entire platform. These growth goals would require thinking about quality in a new way, but Eventbrite’s Frontend Platform team knew their previous system would not support their growth. “Before Bugsnag, all of our JavaScript errors were put into Splunk, and it was just a pile of errors. It was very difficult to sort through or even get any visibility into. There was no grouping or ability to see what was actually impactful, and it was mixed in with all other error messages and logs as well,” says Senna Bala who manages the Eventbrite QA team. “I would spend time trying to force people to look at errors because no one would do it proactively on their own when it’s just so difficult to do.” Since they are responsible for helping engineering produce high quality software through testing and release support, this caused a lot of problems for her team. At the time, the most common way to discover bugs was when they were reported by customers experiencing difficulty with their platform. It’s important to remember that for each user who complains about a bug, there are countless others who also experienced it and abandoned a product. Ben Ilegbodu, Principal Frontend Engineer, explains that their team was even suspicious of errors negatively impacting some of their business metrics, like conversion, but there was no way to know with certainty because of the lack of visibility into errors. Gaining Peace of Mind Enables More Agile Development at Eventbrite In the end, Eventbrite chose Bugsnag to monitor all frontend applications because of its superior user experience, like the ease with which they are able to find specific errors using custom filters. Senna and Ben agree the best thing they have gained from using Bugsnag is the tremendous peace of mind it brings their teams. “Now I can be confident that everything is going into Bugsnag, and we can actually see the number of users that are hitting a bug, the number of different events. We get such granular data that I know I can go in there and find errors that are impactful.” - Senna Bala, QA Enginerring Manager The ability to know about errors before they negatively impact customers has helped them speed up their release process. “In a sense it’s kind of like a safety net. If there’s a problem, we know we’re going to catch it. We are trying to move in a more agile way, where we can just decide to put something out to 5% of users and see how it goes. We can slowly release it out and check Bugsnag to see if there are any issues users are experiencing. This helps us move quicker since we don’t need to make sure everything is perfect before showing it to anyone, and we can get feedback early in terms of user experience and errors,” says Ben. When issues do arise, they are fixing them much faster. According to Ben, having Bugsnag “is the difference between fixing bugs and not fixing them. It’s infinitely faster.” Improved Pre-production Testing and Smoother Releases Using Bugsnag has empowered the QA team to improve their processes and facilitate smoother releases. Running test flights have been significantly sped up, and when they do find errors, they are able to easily reproduce them using Bugsnag’s automatic breadcrumbs. “It is incredibly helpful for QA to be able to provide steps to reproduce because it means there’s a 90% chance it’ll get fixed. Without steps to reproduce, it’s more like a 5% chance because it requires so much work from the developer to dig into and find out why or how it’s happening," says Senna. “JavaScript errors in particular are so edge-casey and hard to reproduce, and we’ve really appreciated having breadcrumbs that actually lay out step by step what a user did to get into this weird state that caused an error.” -Senna Bala, QA Engineering Manager Eventbrite now uses custom filters to monitor releases which has made shipping new features a much smoother process. During a release, new code is only deployed to one server which lets them monitor and fix issues while they are isolated. Eventbrite configured a custom filter in Bugsnag to filter errors by server so they can focus on the release and remove other noise from their view. When a release goes out, the engineers use this filter and monitor incoming errors on the server. This has helped them improve their releases and prevent rollbacks. “We’ve been able to catch a few errors that we wouldn’t have found in our QA process otherwise and been able to resolve those quickly rather than waiting for a customer to report them after a release.” DOWNLOAD CUSTOMER STORY PDF Also published . here

BUGSNAG

bugsnag.com

-- employees

Since 2013

COMPANY RANKING

BUGSNAG

EVERGREEN INDEX #2028

Representing this company? Click here to claim and customize this page!

bugsnag WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

BUGSNAG

bugsnag.com

-- employees

Since 2013

COMPANY RANKING

BUGSNAG

EVERGREEN INDEX #2028

RELATED COMPANIESRANK

STORIES ABOUT BUGSNAG

Representing this company? Click here to claim and customize this page!

bugsnag WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!