5 ms·
At least two (another one in Melbourne strangely enough) * https://linc.sh/ https://linc.sh/ * https://featurepeek.com/ https://featurepeek.com/ Both of these
by Rodeoclash 7y ago
At least two (another one in Melbourne strangely enough)
* https://linc.sh/ https://linc.sh/
* https://featurepeek.com/ https://featurepeek.com/
Both of these are frontend only feature previews however, they assume an available backend to connect to the frontend code. My tool (Stagehand) will preview the entire stack, provided you can run your setup in Docker. Considering the last three places I've worked all used Docker Compose to run the local development environment and Docker in the CI pipeline, it was a no brainer to use it for the previews as well.
My main differentiator, aside from running the full stack, you can also run supporting services alongside the preview. In our case, we run an emulated S3 endpoint and a tool to catch outgoing mail (it poses as an SMTP server). This means that if you're testing a piece of functionality that uploads to S3, you can easily complete the action then change to the S3 emulator and see the file is uploaded to the correct place. Likewise with the email catcher, it makes it really easy to see invite emails being sent out, or welcome emails after signup.
Other examples might include a frontend to your database, e.g. PGAdmin, so you could directly change the database in the preview then test the result.
The original use case was so that I could easily share my work with others in my 9 - 5 job. However, as I've taken more responsibility over the team here I'm using it more for testing others work before it gets merged to master.
If anyone would like to trail it, I've made a Google Form here you can put your name on: https://forms.gle/cMB2mDbt5342bQ8P9 https://forms.gle/cMB2mDbt5342bQ8P9
While the system works and is stable, documentation is ...non existent. I'd need to help you get setup to use the service (and it would give me an excuse to write the docs as I do it)