Architecture testing can be a daunting task – especially for devs who aren’t in the habit of testing architecture from the very beginning and continuing to do so as their deadline approaches. We’re here to tell you that it’s really worth the effort and save you a ton of time and tears in your next project.
Table of contents
Why test the architecture? Here are 6 basic reasons:What does architecture testing look like in practice?Let’s start with some basic information about the projectNon-functional requirementsFirst step – proof of concept!Proof of concept completed – time for some architecture testsConclusionsFinal words: What has this project taught us?Bonus round: a recap of tools we used for architecture testingSort: