PerfAgents

We are live on Product Hunt! Click the link below to check it out: https://lnkd.in/g7cARkqZ #producthunt

🎊 Excited to share that we are launching on Product Hunt soon! 🔔 Click the link below to get notified about the launch. https://lnkd.in/gxzj4yCM

The next time you hear about an outage or a downtime issue within your company, you need to ask your guys a question! Do we have synthetic monitoring in place? #outages #downtime #syntheticmonitoring

Testing and monitoring your customer-facing applications should replicate your user's behavior (as closely as possible)! Why so? --> To avoid outages, slowness/latency, and P1 issues. Suppose you anticipate that the top set of sequence of actions your users do on your web application is this: --> User logs in to the application --> User click on the search tab in your application and type in a keyword. --> Search results show up --> Performs some activity --> Logs off The above flow is never guaranteed to work for all users. Even if it works, some users could experience slowness. That's because modern applications are way more complex than legacy ones and have many moving parts. One user could access it using a Chrome browser on a Windows laptop from New York, whereas another would access it through a Safari browser on a Mac from Portland, OR, and so on. To ensure that user flow for every user works from their locations and from their devices and browsers, you need to proactively and continuously check whether that flow is working as expected and whether SLAs are met all the time. That's where synthetic monitoring concepts come to the rescue. How you do that is like this: You need to script that exact user flow using a test credential or test user account and then run that script continuously from AWS regions closer to the user's location. That way, you know that it works from the AWS region and, in turn, be sure that it will most likely work for any users around that region. It's a simple but powerful technique to ensure users have a great experience using your product. All that you have to do are: 1) Write a Playwright script to mimic that user's action 2) Push it to your GitHub repos 3) Create a PAT with read-only access 4) Create a PerfAgents account and click "Create Sequence Monitoring." 6) Click on "Playwright" and choose "GitHub Integration." 7) Insert the PAT information from GitHub 8) Select the Amazon Web Services (AWS) region and the frequency at which you want your script to run. 9) Select the notification endpoint (Jira/Slack/Email/Linear/AWS S3 Bucket or whatever. PerfAgents supports a lot of such integrations) 10) You will be alerted if there are SLA breaches or outages. If not, PerfAgents shows Splunk-like Logs where you can see what is running and what has run. You can also see Forensic data around your monitoring script execution, deep-dive into traces, and a lot more data. PerfAgents - The only infrastructure software you need to monitor your software in just the way people use your software! PerfAgents is built to run open-source web automation software such as Playwright and Selenium. Gone are the days when you need to spend millions of dollars to monitor and still zoom into P1 issue calls in the middle of the night. Embrace open source and get 100% monitoring coverage for your user flows! #perfagents #opensource #playwright

Monitor the software just the way people use it! PerfAgents is built to make software testing more user-centric and aligned with real-world scenarios. You can repurpose these tests for synthetic monitoring! #end-to-end-testing #qa #devops

Writing proper tests (synthetic or functional) is essential. Here's how tests can reveal design issues: Nightmare Setup: If setting up your tests feels like assembling a spaceship, your code is likely too complex. Mock Madness: Overusing mocks suggests your code is too tightly coupled and lacks clear boundaries. API Confusion: Unclear API signatures make your code hard to understand and use correctly. Test Chains: Tests that depend on each other become fragile and difficult to maintain. Test Troubles: Slow, flaky, or frequently breaking tests indicate deeper issues in your code's design. #functionaltests #synthetictests #syntheticmonitoring