Interesting, but this needs to be integrated into CI, not Slack, to be taken seriously by teams larger than just a few people. And arguably, I tend to set up CI of any serious project before it goes to production.
Show HN: Spotbot, a Slack bot that monitors your website for visual bugs
51–60 of 60 posts
Re: Show HN: Spotbot, a Slack bot that monitors your website for visual bugs
#52Interesting, but this needs to be integrated into CI, not Slack, to be taken seriously by teams larger than just a few people. And arguably, I tend to set up CI of any serious project before it goes to production.
What's your CI system of choice?
Re: Show HN: Spotbot, a Slack bot that monitors your website for visual bugs
#53I understand slack integration for some tools, but is this slackbot-as-a-product thing going to become the new fad? What if I want to use your tool without using slack?
We plan on supporting other workflows soon, we just started with Slack cause that's what we use. Next stop is probably email. Any other integration you'd like to see?
I've worked with many systems like this and know that notifications are too easy for individuals to ignore. Your primary action should be to open an issue in a bug tracking system, and let that system trigger the email/instant notification. This helps teams get a better picture of bug volume/impact/area over time, allows for prioritization of work and ensures issues don't get lost during major bug storms.
Also, being able to link a bug conclusively to a changeset, build or a deployment ID would be very valuable. Rather than building lots of deep CI integrations, you could do this by allow users to configure your monitor to look for version numbers in server hints (headers, hidden fields, status pages, etc).
Re: Show HN: Spotbot, a Slack bot that monitors your website for visual bugs
#54What if my website isn't published yet? Is it possible to run this locally for a locally deployed website/webapp.
Re: Show HN: Spotbot, a Slack bot that monitors your website for visual bugs
#55I understand slack integration for some tools, but is this slackbot-as-a-product thing going to become the new fad? What if I want to use your tool without using slack?
We plan on supporting other workflows soon, we just started with Slack cause that's what we use. Next stop is probably email. Any other integration you'd like to see?
How about an RSS feed?
Re: Show HN: Spotbot, a Slack bot that monitors your website for visual bugs
#56I tried it with our product and it took a snapshot before all of the (wall time intensive) api calls finished. Is there a way to configure it to wait a few seconds?
Not currently, but this is a common request. What would you prefer: - A javascript object being injected into your page that you could call to indicate the page was done - A setting within the UI that would allow you to configure a wait time
Instead of injecting something into the page, what about having the snapshotter running an is-it-done-yet callback periodically to see whether it returns true? That would allow some basic checks like "is this particular DOM element visible yet" or "how many entries are in this list" without needing to modify the production code in the page.
Re: Show HN: Spotbot, a Slack bot that monitors your website for visual bugs
#57I understand slack integration for some tools, but is this slackbot-as-a-product thing going to become the new fad? What if I want to use your tool without using slack?
Yep, same here FYI. I was bummed to see slack-only signup, and stopped because I didn't want to share my teammates' profiles.
Re: Show HN: Spotbot, a Slack bot that monitors your website for visual bugs
#58Interesting, but this needs to be integrated into CI, not Slack, to be taken seriously by teams larger than just a few people. And arguably, I tend to set up CI of any serious project before it goes to production.
What's your CI system of choice?
I really like Circle CI, but I've used (and enjoyed) most of the other services as well.
Re: Show HN: Spotbot, a Slack bot that monitors your website for visual bugs
#59I tried it with our product and it took a snapshot before all of the (wall time intensive) api calls finished. Is there a way to configure it to wait a few seconds?
Not currently, but this is a common request. What would you prefer: - A javascript object being injected into your page that you could call to indicate the page was done - A setting within the UI that would allow you to configure a wait time
I don't really care about all of the calls, but I'd like to say "here's a regex pattern describing a uri. once any connection with uri pattern closes (within 10 seconds), you can render."
Yeah, this isn't great for websockets/long polling or other persistent methods, but it's fine for simple ajax-y calls.
Re: Show HN: Spotbot, a Slack bot that monitors your website for visual bugs
#60I can't really say as to whether this is due to load, or some underlying problem, but it seems that - currently - if you just wait around for the system to get to your requested (free) screenshot, it ticks down to 4 Screenshots ahead of yours, and... Nothing.
Not a single one of the boxes seem to update anymore. They all just say 4 screenshots ahead of yours. It seems, I spoke a bit too soon. Something is happening now. I guess my cynicism got the better of me when they all hit 4 and just... Stopped :)