Testing

Reflecting on an excellent evening talking about testing serverless in the serverless meetup.

It struck me that people are still asking the wrong question.

"How do I test the code I've written", needs to be replaced by, "How do we test our service?"

"The best architectures, requirements, and designs


emerge from self-organizing teams", we're told in the Agile Manifesto.

Surely it's time to include testing in this?

Let the team test their own code, but do not, ever, allow an engineer to develop their own tests, pass that responsibility to someone else in the team. Engineers will only ever build tests that pass their code, a second set of eyes will, by definition, view the problem differently and spot way more problems as a result.

要查看或添加评论,请登录

Mike Charles的更多文章

  • Someone Broke the Internet (Again)

    Someone Broke the Internet (Again)

    It all started back in November of course, when Kim Kardashian’s butt broke the Internet. (Except that it didn’t break,…

    1 条评论
  • Highly Available Luck

    Highly Available Luck

    Highly Available Luck The established architectural approach when designing infrastructure to is to work top-down. For…

    3 条评论

社区洞察

其他会员也浏览了