How do you integrate SmartBear tools into a CI/CD pipeline to achieve faster ?
I’m exploring ways to integrate SmartBear tools into a CI/CD pipeline to improve both speed and reliability in automated testing. Based on your experience, what approaches, configurations, or best practices have helped you successfully incorporate tools like TestComplete, ReadyAPI, or Zephyr into your CI/CD workflow?”Best practices for stabilizing DéjàClick selectors ?
Hi everyone! I’m managing a suite of AlertSite UXM monitors for our React-based application. We’ve been running into a recurring issue where our DéjàClick scripts fail with an 'Object Not Found' error immediately after a new production deployment—even when the UI looks identical to the user. It seems our build process is generating dynamic CSS hashes (e.g., .button-a7x9) that break the recorded XPaths/Selectors.
Quantity of Passes for Clear Notification
Today, AlertSite allows the user to configure the number of consecutive errors before an alert is generated. Unfortunately, it does not offer similar functionality to specify the number of consecutive passes for the error to clear. As soon as a monitor passes, AlertSite sends a clear message to integrations, such as PagerDuty. It would be helpful if AlertSite allowed the user to specify the number of consecutive passes for the error to clear under the Edit Alert Recipient setting.
Blackout at system/account level instead of monitor level
Hi. New feature suggestion regarding blackouts... We have maintenance days scheduled throughout the year where we create a blackout using the bulk settings for all monitors. Even though we know the schedule for the entire year in advance, we cannot setup the blackouts in advance for the entire year because the blackouts are done at the monitor level. Meaning if I wanted to setup a blackout for an event three months from now, I can only select the monitors that exist at the time I'm entering the blackout. If any new monitors are created between the time the blackout was entered and when it actually takes place, they would not be included. Having a way to blackout at the account/system level that would include anything not yet created would be helpful.
Default Behavior for Monitors NOT in a Recipient Group 2022
Recipient Groups UXM (or Notifier Groups in AlertSite 1.0) allow you to define who will be notified when an alert for a specific device is triggered. The default behavior for any monitor that is not assigned to a group, is to notify all contacts on the recipient list according to the rules defined for each. It does not matter if a specific contact is in a group or not, the behavior is dictated based on the monitor disposition, not the recipients. Once a monitor is assigned to at least one recipient group, it will only notify recipients assigned to that group. Monitors can be associated with as many groups as you like, as can recipients. In the UXM console, you can configure a default group by navigating to the Alerts Tab > Recipient Groups screen. Next to the heading of any recipient group, Click the Flag icon next to a recipient group you would like to assign as the default group. In the AlertSite 1.0 console, you can tell which monitors are assigned to a notifier group under the Configuration tab. Any monitor that has the icon with the computer folders next to it is assigned to at least one group. In AlertSite 1.0, you can configure a default recipient group under the notifier groups configuration menu by navigating to Notifiers > Notifier Groups screen > Then clicking the Notifier group heading. Under the notifier group edit screen in 1.0, check the option for "Default Group will be used for all unassigned site" and click "Submit" button at the top right hand corner. Under the Account Preferences tab of the settings menu (Both UXM and 1.0 console) you can also disable notification for any new monitor you create by default. You can modify the settings for each monitor individually if needed. Another popular way to work around the default behavior is to create one 'Placeholder' group and assign all monitors to it, new and old. In this way, you can be sure that the wrong people are not notified if an error is triggered. You can then assign an invalid notification contact to the Placeholder group as well, or a contact who should be notified for all errors if one exists.
