In this talk I will dive into the choices we at Neat have made in our test architecture in order to both preserve and create value for our company, customers and software development teams.

I will go through detailed, concrete choices in test code and move onward to the organization of frameworks, tools, processes and practices. I will cover the measures we have intentionally chosen in order to catch regressions, reduce false positives, write maintainable tests, understand test results and enable development teams to do their job faster and with increased confidence. While our specifics, embedded software and end-to-end tests written in Python may not match your situation, many of the questions we asked in order to determine the choices we have made are likely to be both relevant and perhaps even unthought for other teams.

Test architecture encompasses everything from code to more theoretical concerns like enterprise architecture, but with concrete, immediate consequences. Ignore it at your peril or at least come and find out that it’s a rich, challenging and rewarding domain.