Automated tests and non-functional requirements are two widely used terms in the software development sector. Both are essential for software development teams but rarely mentioned together. Today, most software development teams are utilizing the development practice continuous integration. A method where software is built in iterations and in each iteration small chunks of code are merged into the main repository. Continuous integration requires automated tests to verify that each chunk of code is compatible with the main chunk. Automated test is essential for continuous integration to detect anomalies in each chunk of code. Customer satisfaction is a result of how well the delivered product performs in terms of non-functional requirements. Although the term “non-functional requirement” has not been formally defined and the existing definitions are diverse. In this thesis, we define the non-functional requirement, response time with help from a user-centered evaluation of responsiveness study. We create a test suite that can be ran on an automated build with focus on user-action-response. Based on the test result and a conducted survey, we evaluate how aware developers are when it comes to causes to performance issues.