CRcreichert·May 11, 2017Submission
Show HN: Automate Smoke-Tests for a Go API Using Heroku Review Apps
3 points · Open discussionassertible
go-heroku-example
Go2017–2017
assertible / go-heroku-example
go-heroku-example
Create an automated smoke-testing pipeline with Go, Heroku Review Apps, and Assertible
2Distinct people
2Mentions
1Explicit recommenders
5GitHub stars
What to know before exploring
What it is
Create an automated smoke-testing pipeline with Go, Heroku Review Apps, and Assertible
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
We've been working on API test automation for a while and this is one of my favorite integrations so far. The idea is that, after deploying from CI or a script, Assertible runs…
CodyReichert used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by 3-hour interval2 dated mentions
Observed mentions: 2017-05-09 16:19:48 UTC to 2017-05-11 16:25:13 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| May 9, 15:00 | 2017-05-09 15:00:00 UTC | 2017-05-09 18:00:00 UTC | 1 | 0 | 1 |
| May 9, 18:00 | 2017-05-09 18:00:00 UTC | 2017-05-09 21:00:00 UTC | 0 | 0 | 0 |
| May 9, 21:00 | 2017-05-09 21:00:00 UTC | 2017-05-10 00:00:00 UTC | 0 | 0 | 0 |
| May 10, 00:00 | 2017-05-10 00:00:00 UTC | 2017-05-10 03:00:00 UTC | 0 | 0 | 0 |
| May 10, 03:00 | 2017-05-10 03:00:00 UTC | 2017-05-10 06:00:00 UTC | 0 | 0 | 0 |
| May 10, 06:00 | 2017-05-10 06:00:00 UTC | 2017-05-10 09:00:00 UTC | 0 | 0 | 0 |
| May 10, 09:00 | 2017-05-10 09:00:00 UTC | 2017-05-10 12:00:00 UTC | 0 | 0 | 0 |
| May 10, 12:00 | 2017-05-10 12:00:00 UTC | 2017-05-10 15:00:00 UTC | 0 | 0 | 0 |
| May 10, 15:00 | 2017-05-10 15:00:00 UTC | 2017-05-10 18:00:00 UTC | 0 | 0 | 0 |
| May 10, 18:00 | 2017-05-10 18:00:00 UTC | 2017-05-10 21:00:00 UTC | 0 | 0 | 0 |
| May 10, 21:00 | 2017-05-10 21:00:00 UTC | 2017-05-11 00:00:00 UTC | 0 | 0 | 0 |
| May 11, 00:00 | 2017-05-11 00:00:00 UTC | 2017-05-11 03:00:00 UTC | 0 | 0 | 0 |
| May 11, 03:00 | 2017-05-11 03:00:00 UTC | 2017-05-11 06:00:00 UTC | 0 | 0 | 0 |
| May 11, 06:00 | 2017-05-11 06:00:00 UTC | 2017-05-11 09:00:00 UTC | 0 | 0 | 0 |
| May 11, 09:00 | 2017-05-11 09:00:00 UTC | 2017-05-11 12:00:00 UTC | 0 | 0 | 0 |
| May 11, 12:00 | 2017-05-11 12:00:00 UTC | 2017-05-11 15:00:00 UTC | 0 | 0 | 0 |
| May 11, 15:00 | 2017-05-11 15:00:00 UTC | 2017-05-11 18:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sourcesWe've been working on API test automation for a while and this is one of my favorite integrations so far.
The idea is that, after deploying from CI or a script, Assertible runs a series of integration/smoke tests against the app and reports the result back to GitHub via a status check.
Here's an example of a failing status check on a Go API: https://github.com/assertible/go-heroku-example/pull/5
Having immediate feedback on an actual live deployment has saved us a lot of time from manual testing.
Would love to hear your thoughts!
In Show HN: View API test results on GitHub status checks