28 karma · joined January 3, 2009
I wish people would think about the data they use for the tests a bit more, and how they can create it from scratch in a consistent and scalable way, that way they can always be testing against a clean environment with a known setup and avoid doing a bunch of bad things (like creating data on the fly as part of a test)
So I'm curious, how do you all manage the seeded test data that you need for your QA tests?
I'm glad to see they were able to get this fixed, it'd been bothering me for a little while now. Shortcuts (ctrl+c) still worked, but it was always a bit weird to see Copy grayed out when I had something selected.
For the more straightforward tasks it probably would do well at, copilot seems like the better solution since it's much more tightly integrated into my developer environment.
It's mentioned in the article, but base64 includes weird characters that might not be allowed in a name field, like `+=/`. I also wouldn't be surprised if the airline name field didn't allow numbers.
Reminds me a bit of this post: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
As a bonus one of those contest systems allows users to upload a profile photo, which would greatly increase the bandwidth!
https://github.com/ChrisZieba/dodgercms
Regardless, I think this is something that would be awesome to have. You can even throw in some AWS Lambda if you want to move some stuff out of the browser(like generating thumbnails/index pages/etc). Or just use Lambda to run a complete static site generator(like jekyll or pelican) every time the content in an S3 bucket changes.
Note: I've never actually used either of these, but I did spend a fair amount of time researching this type of stuff.
It helps make up for the slow read speed of many cheap flash drives by caching everything before a user even sits down to use it.(I run a programming contest so we set the computers up and boot them before hand, plenty of time for vmtouch to do its job)
The only thing I can think of is that AWS Certificate Manager only validates by email addresses which can be problematic if you don't have MX records or don't have control over it(Maybe a large organization where the people who do control those email addresses won't click simple verification links)
It seems a bit inconsistent as to when it will use the email on the whois record for the validation too. For some subdomains I try it will allow validation using the whois address, other times it's just the common aliases@sub.domain.com(which requires an mx record) So I guess if you're nesting deeper than one subdomain(e.g. abc.def.example.com) then maybe it'd be easier to get letsencrypt set up than try to get mx records for abc.def.example.com.
Shameless Plug/Disclaimer: I had been working on a tool to make it dead simple to use Lets-Encrypt certificates for CloudFront/ELBs and handled autorenewal via Lambda. I'm not sure there is any use for this now that this exists though.
The entire website is open source, including the data files(and some of the tools used to gather/create the data files) so if you require something more powerful than the api provides you can create it yourself.