<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Integration-Testing on Scholion</title><link>https://scholion.thluiz.com/tags/integration-testing/</link><description>Recent content in Integration-Testing on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Sat, 10 Jun 2017 14:32:38 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/integration-testing/index.xml" rel="self" type="application/rss+xml"/><item><title>How to build complex user interfaces without going completely insane</title><link>https://scholion.thluiz.com/notes/how-to-build-complex-user-interfaces-without-going-completel/</link><pubDate>Sat, 10 Jun 2017 14:32:38 -0300</pubDate><guid>https://scholion.thluiz.com/notes/how-to-build-complex-user-interfaces-without-going-completel/</guid><description>The article recommends delaying state updates in dialogs, separating model data from UI state, and favoring integration tests over unit tests when building complex web interfaces.</description></item></channel></rss>