Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Automatically create QA environments for your GitHub pull requests

prune.io

Post reply on HN
Print view View original

1–10 of 21 posts

Re: Show HN: Automatically create QA environments for your GitHub pull requests

#4

Post by adambouchard »

mpotter wrote: post #2

Dev here. Our team has grown to love the GitHub pull request workflow. We built Prune to solve one issue we consistently run into: how to QA on the various branches before merging. Happy to answer questions and thanks for any feedback!

looks awesome

Re: Show HN: Automatically create QA environments for your GitHub pull requests

#5

Post by jawns »

mpotter wrote: post #2

Dev here. Our team has grown to love the GitHub pull request workflow. We built Prune to solve one issue we consistently run into: how to QA on the various branches before merging. Happy to answer questions and thanks for any feedback!

Can you give more details about Visual Regression Testing? If you're comparing screenshots, how do you account for dynamic content?

Re: Show HN: Automatically create QA environments for your GitHub pull requests

#6

Post by mpotter »

jawns wrote: post #5
mpotter wrote: post #2

Dev here. Our team has grown to love the GitHub pull request workflow. We built Prune to solve one issue we consistently run into: how to QA on the various branches before merging. Happy to answer questions and thanks for any feedback!

Can you give more details about Visual Regression Testing? If you're comparing screenshots, how do you account for dynamic content?

Sure! We use a web driver to simulate browsing in an actual client, so Javascript, etc. is executed as it normally would be.

Re: Show HN: Automatically create QA environments for your GitHub pull requests

#7

Post by jawns »

mpotter wrote: post #6
jawns wrote: post #5

Earlier quoted context omitted.

Can you give more details about Visual Regression Testing? If you're comparing screenshots, how do you account for dynamic content?

Sure! We use a web driver to simulate browsing in an actual client, so Javascript, etc. is executed as it normally would be.

But what about content that changes on each page load, like a timestamp or a rotating banner ad? Would that be flagged as a regression?

Re: Show HN: Automatically create QA environments for your GitHub pull requests

#8

Post by masklinn »

That's pretty nice, although... since there are already environments to run tests (e.g. travis) why run them again in Prune, and why not wait until the QA environment is setup to display the notification?

I dig the visual regression thing, though I fear combinatorial explosion for big-ish changes if it goes through the whole site or application.

Re: Show HN: Automatically create QA environments for your GitHub pull requests

#9

Post by antjanus »

mpotter wrote: post #2

Dev here. Our team has grown to love the GitHub pull request workflow. We built Prune to solve one issue we consistently run into: how to QA on the various branches before merging. Happy to answer questions and thanks for any feedback!

I just wanted to know how this works. Our company uses a pretty neat setup where we run different different branches under a wildcard domain on a single machine.

Basically, we run a *.staging.domain.com; however, databases are always tied together. (This is for Wordpress purposes). We use [Genesis](https://github.com/genesis/) to achieve this effect.

So, do you guys work similarly to Travis-CI in that you run an instance, follow instructions in a file and how to provision and setup the site, and then instead of just running a unit test (like travis), you keep the instance running and expose it to public?

Do you use virtualization or docker instances? (Just curious!) How long do you keep them up and do you suspend the instances when it becomes disused? Will you be able to run a single instance at a time or many? (meaning, one branch at a time or will you have 20 environments setup for my 20 pull request).

In the future, will you support private repos?

Thanks! This looks REALLY badass! :)

Post reply on HN