Testdown.org Cilia.io
There appear to be more robust alternatives for both of these, so I’m curious what your “elevator pitch” would be for them?
The one little feature it has that I haven't seen in other tools (but I'm sure it's not unique) is that it can reverse proxy by Git commit, so that ".ci.example.com" becomes a way to see how the frontend looks at some particular revision.
Actually I wouldn't really pitch it to anyone, because it was quite internal and somewhat made in anger over the complexity of build servers like Jenkins. It was also an exercise in slightly larger-scale shell programming, which is considered extremely stupid around here, so.
Testdown is still the best system for smoke testing React apps I've used, and I made it because the company I was working at really had horrible experiences with frontend testing. The natural language specifications are kind of like Cucumber, except better and with no need to code step definitions, just define the "data-role" attribute on elements, which I found to be a much nicer paradigm than maintaining a bunch of CSS selectors in the test code, etc.
It was really useful to have UI test specifications that could be read by everyone in the company. And because it's made in a way that integrates with the React app, instead of sitting outside watching via e.g. PhantomJS, it can be very accurate and robust. For example, our app showed a spinner whenever it was loading an AJAX call, so we came up with the "Wait." command that simply waits until no spinner is visible, and that worked really great.
I don't care so much about Cilia, but Testdown is still a really interesting project for me. It's as much about a specific implementation as a way of thinking of testing in a pragmatic and nice way. I'd like to try implementing it with a parser based on GF (Grammatical Framework), to be able to handle actual grammatical constructs with more sophistication.
Neither of these projects are mature technology, but they worked like champs internally for about a year, and helped kickstart us into continuous integration of the frontend, which had been a thorny problem.