We rolled out some complex custom contexts today, and our testing process devolved into our engineers firing events, and then us running the EMR ETL and checking the enriched-bad folder on S3 for any problems.
I’m sure there’s a better way - how do you solve this problem?

Another option (in addition to what @njenkins has mentioned above) we use is to test and validate all schemas by first pushing them to Iglu on a Snowplow Mini instance (using igluctl) before pushing them into production. This allows us to validate that the data will be enriched/processed correctly and that the result that is populated in Elasticsearch is what we expect.