# How trivago performs non-functional testing on every commit

DevFeed: [How trivago performs non-functional testing on every commit](<https://devfeed.tech/articles/building-fast-and-reliable-web-applications-27962.md>)

Original publisher: [Read original article](<https://tech.trivago.com/post/2018-10-12-rapidfirenonfunctionaltes/>)

Author: Frank Van Gemeren

Published: 2018-10-12T00:00:00Z

Content type: article

Language: en

Sources: [Trivago](<https://devfeed.tech/sources/trivago.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [web applications](<https://devfeed.tech/topics/web-applications.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Accessibility](<https://devfeed.tech/topics/accessibility.md>), [Availability](<https://devfeed.tech/topics/availability.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [availability](<https://devfeed.tech/tags/availability.md>), [backend](<https://devfeed.tech/tags/backend.md>), [code-coverage](<https://devfeed.tech/tags/code-coverage.md>), [devops](<https://devfeed.tech/tags/devops.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [release-engineering](<https://devfeed.tech/tags/release-engineering.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [testing](<https://devfeed.tech/tags/testing.md>), [web](<https://devfeed.tech/tags/web.md>), [web-applications](<https://devfeed.tech/tags/web-applications.md>)

## AI overview

This article explains why testing should cover non-functional requirements such as performance, capacity, availability, scalability, and accessibility. It describes trivago's approach to making non-functional testing visible to developers on every commit and discusses the challenges of providing early feedback in a large codebase.

## Source excerpt

Testing your functionality is important, but what happens if other factors come into play? In this blog post we show how trivago handles non-functional testing for every commit and how we scaled it.