There's no mention about pricing... any rough idea/estimation?
Hey! Good question, we're still working out the details on pricing but I want it to be very reasonable, simple and transparent for people. Just need some time to work through with a few initial beta testers. Stay tuned!
Show HN: Percy.io, a continuous visual integration tool
41–50 of 57 posts
Re: Show HN: Percy.io, a continuous visual integration tool
#42Devil's advocate - won't this tend to bolster the outdated attitude that the front end must be pixel-perfect?
Re: Show HN: Percy.io, a continuous visual integration tool
#43This looks promising. Our project has a plethora of selenium tests, but they're focused on functionality only, not appearance. We can tell there is a table, button, link, form, etc. and click it. On that side we're reliable. But we really let ourselves down sometimes with regressions to the look and feel of the application. Are there any competitor tools for this visual testing ?
Re: Show HN: Percy.io, a continuous visual integration tool
#44Devil's advocate - won't this tend to bolster the outdated attitude that the front end must be pixel-perfect?
I'm not sure I consider that to be true. Why is pixel perfection out-dated?
Re: Show HN: Percy.io, a continuous visual integration tool
#45Earlier quoted context omitted.
I'm a member of organisations that may not be comfortable with me giving permission by proxy. I couldn't find a way to sign up and exclude private repos or organizations.
Fair enough, but I think that's a limitation of Github rather than a problem imposed by Percy.
How is that not a problem imposed by Percy?
I'd feel more comfortable having a different mechanism to request an invite.
While the permissions don't grant Code Access, it does ask to read Organization and Team membership. I'd expose data for every member of my companies github organization to Percy, JUST for an invite.
Re: Show HN: Percy.io, a continuous visual integration tool
#46Earlier quoted context omitted.
Fair enough, but I think that's a limitation of Github rather than a problem imposed by Percy.
Percy.io's Invite Request system is tied to github. How is that not a problem imposed by Percy? I'd feel more comfortable having a different mechanism to request an invite. While the permissions don't grant Code Access, it does ask to read Organization and Team membership. I'd expose data for every member of my companies github organization to Percy, JUST for an invite.
Re: Show HN: Percy.io, a continuous visual integration tool
#47Earlier quoted context omitted.
Percy.io's Invite Request system is tied to github. How is that not a problem imposed by Percy? I'd feel more comfortable having a different mechanism to request an invite. While the permissions don't grant Code Access, it does ask to read Organization and Team membership. I'd expose data for every member of my companies github organization to Percy, JUST for an invite.
Percy is a tool that integrates with Github to set build status on Github pull requests. Of course it needs to tie into Github.
However:
Sign up for Service != Sign up for Invite.
Re: Show HN: Percy.io, a continuous visual integration tool
#48Earlier quoted context omitted.
Percy is a tool that integrates with Github to set build status on Github pull requests. Of course it needs to tie into Github.
100 %. However: Sign up for Service != Sign up for Invite.
Re: Show HN: Percy.io, a continuous visual integration tool
#49This seems like a really convenient way to watch for front-end changes, but how do things like margins work? Will my whole page be red because everything has been shifted around or squished? Responsive capabilities will really improve usefulness, and the absence is somewhat of a deal-breaker. On responsive sites developers will have to eyeball each change even when using Percy, so checking the desktop resolution woul…
Re: Show HN: Percy.io, a continuous visual integration tool
#50Earlier quoted context omitted.
I'm not sure I consider that to be true. Why is pixel perfection out-dated?
Perhaps because rigid constraints are useless with the number of different devices out today, and layouts should instead be highly adaptive?
For example this uses Firefox, if all I change is something in the backend. My front end should look the exact same before the change and after.