CodyReichert

9 ms·

31.
by CodyReichert 9y ago
One of my favorite parts of this is that, after you import a Swagger, you can initiate the tests from CI - effectively validating your API backend after a deployment. Interested to hear what other automation and testing can be done from a S
32.
by CodyReichert 9y ago
I'd be interested to know this as well. I've been solving this problem while building Assertible; generate a suite of API tests from a Swagger spec: https://assertible.com/blog/testing-an-api-using-swagger
33.
by CodyReichert 9y ago
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 a series of integration/smoke tests against the app a
34.
by CodyReichert 9y ago
Another one for Google that's really interesting is their testing blog: https://testing.googleblog.com/
35.
by CodyReichert 10y ago
We created an integration with GitHub that automatically runs tests against a web service when a repository is 'deployed'. In short, this is how the workflow looks: - Push code to GitHub - Build and deploy code on CI - Send a dep
36.
Show HN: Automated post deployment testing for any GitHub repo(assertible.com)
6 points by CodyReichert 10y ago|1 comments
37.
by CodyReichert 10y ago
It's in the works, and will be the greatest workflow of all time ;) In all seriousness though, I'm loving Codeship and it's concept of "pipelines". Really looking forward to working with it more.
38.
by CodyReichert 10y ago
Author here - I'm planning a couple new guides with other CI/CD services (like Codeship). Any thoughts on what pipelines/workflows could use a good example?
39.
by CodyReichert 10y ago
Well he does use an Android, so it wouldn't surprise me if that was 100% correct.
40.
by CodyReichert 10y ago
More like, so you don't use a phone then?
41.
Why (and how) we test every single API deployment
3 points by CodyReichert 10y ago|1 comments
42.
Why we test every single API deployment(assertible.com)
5 points by CodyReichert 10y ago|1 comments
43.
Show HN: Better Slack Notifications for AWS CloudWatch via Lambda(github.com)
5 points by CodyReichert 10y ago|0 comments
44.
by CodyReichert 10y ago
Stripe allows you to store 'metadata' (key/value pairs of arbitrary data) with customers. Wouldn't that work for storing addresses? https://stripe.com/docs/api#metadata
45.
by CodyReichert 10y ago
Hey HN, author here! This method of inlining CSS for email templates has been serving us well for a while now at Assertible. All of our emails are created with React components and then compiled down to static markup; with dynamic data inje
46.
Creating email templates with React components(assertible.com)
6 points by CodyReichert 10y ago|1 comments
47.
by CodyReichert 10y ago
Hey, thanks for the feedback. In the future we hope to allow a bit more functionality before requiring an email to be verified! (FWIW, GitHub login does the verification for you).
48.
Show HN: Continuously testing Heroku GitHub deployments(assertible.com)
12 points by CodyReichert 10y ago|6 comments
49.
by CodyReichert 10y ago
Hey, thanks for checking it out! Glad you were able to see the usefulness of it :) I agree that staging/pre-release testing is really valuable. We want to make sure those uses-cases are supported and just as easy, ideally hooking into
50.
by CodyReichert 10y ago
Thanks for checking it out and for the tips on the landing page! I'll take a look at those. I definitely agree on having focused tools and use-cases; the current plan is to work on better and more valuable assertions and integrating th
51.
by CodyReichert 10y ago
Hey HN, My co-founder and I just released Assertible - a tool for making assertions about your production API and websites. We've yet to find a good solution for testing production API's and we made Assertible to make that not onl
52.
Show HN: Assertible – Test and monitor your production APIs(assertible.com)
6 points by CodyReichert 10y ago|5 comments
53.
by CodyReichert 10y ago
Believe it or not, it's not always that obvious to new (or even seasoned) founders. Heck "going to a conference" still sounds like a good idea -- in reality, talking to some of my existing users about the product fit could be
54.
by CodyReichert 10y ago
Definitely agree. It's easy to think of a cool "new social sharing blah" idea -- but guess what? If you're a new founder, without a large persuasive network to get word out to free users -- you're going to have a ve
55.
by CodyReichert 10y ago
Absolutely, and that's why there is the term "MVP". It's easy to get sucked into thinking "Before anyone will buy it, <x> must be done". That is false thinking 99% of the time. You need to get out a pro
56.
by CodyReichert 10y ago
So I guess my theory is: They make their own UI's to avoid showing copyrighted material -- and would it be fair to say that it's not important enough (to the plot) to hire an expert web designer, so they end up with something like
57.
by CodyReichert 10y ago
Anything specific that you found confusing? I actually thought the first chapter was a great start. I'm sure the authors would appreciate the feedback.
58.
by CodyReichert 10y ago
haskellbook.com is "Haskell: Programming from first principles". Edit: And yes, it's an awesome book.
59.
by CodyReichert 11y ago
Quicklisp is definitely awesome - CL is a million times better with it. You don't need to use Quicklisp to use Qi, but you can definitely use them together. The same is true for cl-project (which I really like). The biggest use-case in
60.
by CodyReichert 11y ago
Hey, author here. YAML was chosen, as another user guessed correctly below, to enable version pinning. ASDF, as far as I knew, did not support any `version` in it's `dependencies` section. A while after the YAML configuration was imple

More ›