AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Splunk transaction examples8/11/2023 Below you will find the details on how to configure the connector for use. This project is supported by the Splunk HTTP Event Collector available in Splunk 6.3 and above. This has been revised as the library has been updated to support both Splunk Cloud and Splunk Enterprise products. The rest of this article will discuss how to get it done. Setting Splunk to show the data you want, dashboards, alerts, email reports etc.Once you come to the step of drilling into a single test report, every point in the dashboard would click over to Perfecto's report, where all of that data exist.īack to the architecture: If you have 1-3, there are only two additions you need to make To read more about the data sent to Splunk, see the article Perfecto-Splunk data schema. Script execution data: script and step-level pass/fail, step names, user experience timing etc.Script meta data: the script name/version, details of the device under test, persona etc.Rather, we bring to your dashboard the essential data to allow you to trend, alert etc.: All of which you can, of course, download from Perfecto into your repository. We produce a LOT of data, some of it is rich media (videos, screenshots etc.). It is worth noting that it is not our intention to flood your dashboard/Splunk with ALL of Perfecto data. and your very own dashboard/business intelligence tool, in this example, Splunk.Perfecto's continuous quality lab, made of devices and browsers.Script repository: could be GitHub, SVN etc.A scheduler: could be Jenkins, Visual Studio or any of your choice.Let us show you how! ArchitectureĮssentially the architecture is based on the same tools and processes used by the testing team: As in, less than 5 minute change to your script. Especially if it involves very little effort. Having a separate tool and process, they do not have the visibility they need into app issues in production.Ī mutual tool, team and process to own the application behavior across versions, devices, personas (and any other parameter you want) could come very handy. Lastly, when product management wants to plan the next set of build features (V7), they want to include enhancements to app weaknesses.The dev team is disrupted (recurringly), and it takes much longer to troubleshoot issues. However, using a separate tool and process, the dev team needs to learn what the issue actually is. The operations team need help because the issue is in the application logic, not a server that went down. Users are upset and the business is impacted. The app in production, using the production build (V5) is now down.The team is unable to launch until the operations tool and team are ready. The next build (V6) is ready to launch, but the operations team and tool aren't.The reality of separate teams, tools and process creates roadblocks at many phases, including: The one that's just starting: let's call it V7.The one that's almost done in the sprint: let's call it V6.The one in production: let's call it V5.When you're responsible for the quality of a mobile application, you're usually responsible for 3 versions of the app (at a minimum): The following article will describe the Perfecto approach in more details. This approach is sub-optimal for those organizations wishing to become agile while maintaining high-quality applications. Many enterprises today use separate tools, processes and teams to gain insight on the application health before and in production. Perfecto allows you to gain continuous insight into your application behavior across builds, devices and more, in the dashboard of your choice.
0 Comments
Read More
Leave a Reply. |