<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kate Marshalkina on Medium]]></title>
        <description><![CDATA[Stories by Kate Marshalkina on Medium]]></description>
        <link>https://medium.com/@kalabro?source=rss-3f52a8e1cf8d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*W6gXr6AGzBWxjl84pQP-AQ.jpeg</url>
            <title>Stories by Kate Marshalkina on Medium</title>
            <link>https://medium.com/@kalabro?source=rss-3f52a8e1cf8d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:34:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kalabro/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Testing modern web apps, Part 1: The big picture]]></title>
            <link>https://medium.com/systemseed/testing-modern-web-apps-part-1-2e143f5bfaf4?source=rss-3f52a8e1cf8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e143f5bfaf4</guid>
            <category><![CDATA[decoupled]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Kate Marshalkina]]></dc:creator>
            <pubDate>Thu, 31 Jan 2019 17:53:22 GMT</pubDate>
            <atom:updated>2019-01-31T17:53:22.463Z</atom:updated>
            <content:encoded><![CDATA[<h4>This article is a part of “Testing modern web apps” series:</h4><ul><li><a href="https://medium.com/systemseed/testing-modern-web-apps-part-0-6560146c06e6">Part 0: Automated tests are awesome</a></li><li>Part 1: The big picture</li><li>Part 2: End-to-End testing</li><li>Part 3: API testing</li><li>Part 4: Unit and integration testing</li><li>Part 5: Visual regression testing</li></ul><p><em>Before diving into specific tools and techniques we need to figure out what can be tested in a modern web application and for what reasons developers use one type of tests or another in their projects. In this article, I’ll walk you through the most common phases of building a web application and match them to corresponding types of automated tests. I’ll try to concentrate on the big picture so you can understand the fundamentals regardless of specific tools, frameworks and programming languages. Let’s start our journey now!</em></p><h3>The journey of the button in the decoupled world</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/767/1*avwjht_fo1oPw8Wk-HdTuQ.png" /></figure><p>Imagine that you’ve got a client who wants to have a new CTA button on their website so that their users can quickly do some stuff online. That sounds like a good example of a feature request.</p><p>I’m not going to say that all you need to do is to write a few lines of CSS and JS because it’s simply not true. <br><strong>Modern web apps are complex.</strong> They can contain hundreds of web pages with hundreds of components, integrations and embeds on each page.<br>In the real world, we break down (<em>decompose, decouple</em>) functionality into smaller independent parts to make web development simple again for individual developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvOP5Xi-7Z1PTzFpnrsgdA.png" /><figcaption><em>Decoupled web architecture</em></figcaption></figure><p>For instance, building our new CTA button will most likely include the following phases:</p><p><strong>1.</strong> <strong>Backend implementation</strong></p><p>We may need to write or read data from a database, let site managers edit button label, make a request to a payment gateway or implement any other business-specific logic on the server side.</p><p><strong>2. API endpoint</strong></p><p>Backend logic needs to be securely exposed to clients. In a trivial case, you’ll have just one client: your own frontend written in React or <a href="https://2018.stateofjs.com/front-end-frameworks/overview/">any other frontend framework</a>. Though it’s often a requirement to support multiple clients: web, mobile, partners, etc.</p><p><strong>3. Visual component</strong></p><p>This includes look &amp; feel of various button states according to designs and UX specs.</p><p><strong>4. Frontend implementation</strong></p><p>Frameworks like React have been started as pure view-layer libraries and now they all suggest a rich ecosystem of tools for building competitive web solutions. Developers love these new tools so much that they tend to write more and more logic on the frontend.</p><p><strong>5. Connect 1–4 to each other</strong></p><p>Decoupling introduces an overhead of connecting different pieces of the app together. The better developers understand the entire architecture of the app, the easier it is to plug in their modules and components to the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6NfhXaXTkiueIRGD743VWA.png" /><figcaption><em>Building decoupled web apps. Five Phases.</em></figcaption></figure><p>Now let’s map the most popular types of automated tests to the diagram above.</p><h3>Unit tests</h3><blockquote><strong>Purpose:</strong> testing individual (isolated) functions, classes, components on programming language level. <br><strong>Tools:</strong> Codeception, PHPUnit, Jest, Mocha, etc.</blockquote><p>You should be able to find unit tests in almost every popular open source library or framework on GitHub. Unit tests reassure developers that pure functions and components work properly in various scenarios and correctly handle edge cases.</p><p>If you maintain a library (internal or external) and other components/developers rely on it, then you need to cover it with unit tests. We’ll discuss unit testing in the upcoming posts.</p><p><strong>The truth is that you most likely don’t need unit tests in any other cases.</strong> When was the last time you wrote a custom sorting function as part of a client project? It is an edge case, and so are unit tests. You can simply skip unit testing for now and come back to it when your app is covered by other types of tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YY0t8WVhs_IOySdXXBSDZw.png" /><figcaption>Unit tests cover any custom code which can be tested separately of its dependencies.</figcaption></figure><h3>Integration tests</h3><blockquote><strong>Purpose:</strong> testing processes or components to behave as expected, including the side effects.<br><strong>Tools:</strong> Codeception, Jest, Mocha, etc.</blockquote><p>Both integration and unit tests focus on the code: functions and components written in a certain programming language. There is one important difference though.</p><p>In unit tests, we mock all dependencies and external functions to test isolated pieces of code. In integration tests, conversely, we keep most of the dependencies in place and test how well individual units play with each other. It makes integration tests much more useful in real-world web development. We will look deeper into integrations tests in the upcoming posts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sAN-AbvYZw3PGkw2JdS4Fw.png" /><figcaption><em>Integration tests cover multiple processes or components within a single code base.</em></figcaption></figure><h3>End-to-End tests</h3><blockquote><strong>Purpose:</strong> testing the entire system on browser level; behaving like a real user.<br><strong>Tools:</strong> Codeception, TestCafe, Cypress, etc.</blockquote><p>While unit and integration tests focus on testing code, end-to-end tests (sometimes called <em>E2E</em>, <em>Acceptance</em> or <em>Functional</em> tests) focus on testing site features.<br>Instead of executing specific functions, end-to-end tests interact with UI elements rendered in a browser: clicking, typing, submitting, etc.</p><p>These type of tests used to be expensive and hard to set up, but things are constantly improving and today almost every website can afford end-to-end testing to ensure that business-critical features work as expected. We will dive into end-to-end testing tools in my next article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KVKYfKKMMcPdKyRkV1khRQ.png" /><figcaption>Testing the whole application together with End-to-End tests.</figcaption></figure><h3>API tests</h3><blockquote><strong>Purpose:</strong> testing API endpoints on HTTP client level.<br><strong>Tools:</strong> Codeception, Postman, SuperTest, Frisby.js, etc.</blockquote><p>If your API endpoints work as expected, then most likely your backends and backend-frontend connections work as expected too. Similarly to end-to-end testing, API testing doesn’t require any mocking-up which produces more realistic results. At the same time, API tests are much faster than end-to-end tests, because they don’t require rendering pages in a real browser.</p><p>These type of tests are my favorite because of their performance-value ratio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dr5c4SrnmGEwYc8urDpHmg.png" /><figcaption>API testing is a must-have for any API-based app.</figcaption></figure><h3>Visual regression tests</h3><blockquote><strong>Purpose:</strong> taking screenshots and comparing to base images in order to verify visual appearance of web pages.<br><strong>Tools:</strong> Gemini, BackstopJS, Percy, etc.</blockquote><p>There are services which conflate end-to-end and visual regression testing. I find this approach confusing because the purposes of these two types of tests are different. E2E tests focus on testing end-user features on a real website while visual regression tests verify look &amp; feel of individual components in different browsers and viewports. For example, E2E test can verify that the checkout flow works fine on the site. Visual regression tests can verify that form inputs and buttons are rendered as per designs on mobile, tablet and desktop. Maintaining visual regression tests may be a little bit more complex compared to other tests so I’d recommend coming back to them when your app is well-covered by E2E, API, and integration tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cuWHYCcKDGOChZlAcY7XDw.png" /><figcaption>Visual regression testing is focused on look &amp; feel of visual components.</figcaption></figure><h3>Conclusion</h3><p>It is important to look at the big picture of your app and think about what and why you want to test. There are many types and subtypes of automated tests at your service. Most popular are Unit, Integration, End-to-End, API, and Visual regression tests. In the upcoming posts, I’ll take a deeper look at each of them, compare available tools and share my own recommendations for a quick start. Stay tuned!</p><h4>💌 P.S. If you liked the article please visit <a href="https://systemseed.com/">SystemSeed.com</a> and meet the team! If you want to know how else we use tools and tech to better serve our clients email me at <a href="/service/mailto:info@systemseed.com">info@systemseed.com</a>!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e143f5bfaf4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/systemseed/testing-modern-web-apps-part-1-2e143f5bfaf4">Testing modern web apps, Part 1: The big picture</a> was originally published in <a href="https://medium.com/systemseed">SystemSeed</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing modern web apps, Part 0: Automated tests are awesome]]></title>
            <link>https://medium.com/systemseed/testing-modern-web-apps-part-0-6560146c06e6?source=rss-3f52a8e1cf8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6560146c06e6</guid>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Kate Marshalkina]]></dc:creator>
            <pubDate>Thu, 06 Dec 2018 15:53:22 GMT</pubDate>
            <atom:updated>2018-12-06T15:53:22.175Z</atom:updated>
            <content:encoded><![CDATA[<p>A few weeks ago I gave a presentation for the “<a href="https://www.meetup.com/Barcelona-Software-Professionals/events/254816749/">Thoughtful Software Engineering</a>” meetup in Barcelona. The main point of my speech was as simple as this: “Automated tests are awesome!”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hj1mVri7dmqo1N5SUV0rwg.png" /><figcaption>Photo by <a href="https://unsplash.com/photos/CnYwFVQ56Eg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Pradeep Ranjan</a> on <a href="https://unsplash.com/search/photos/love?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>Indeed, there are a few well-known benefits of covering your app with automated tests:</strong></p><p><strong>💚 Quality</strong>. By introducing testing practices to your development workflow, you help yourself write code of higher quality. On one hand, you aim to break the code down into smaller, testable, pieces; on another you need to understand very well how those pieces should work together. This zoom-in/zoom-out exercise helps developers deliver better solutions.</p><p><strong>💚 Reliability</strong>. Scripted tests are resistant to human errors which are so common in manual testing. Although automated tests don’t guarantee that your app won’t have a single bug, they can reassure you that business critical features are working fine. Compare these two bugs: <em>your car radio is broken</em> and <em>the car itself isn’t working</em>. The goal of automated testing is to ensure that the car is always working.</p><p><strong>💚 Reducing costs</strong>. Automated testing enables companies to spend less time on finding and fixing bugs and more on building and delivering value for users. Anything that can be automated, should be automated.</p><p><strong>💚 Documentation</strong>. Similar to how good UX is the best replacement for end user documentation, your automated tests is the best spec for your code. Instead of documenting every non-obvious piece of code in a readme file or wiki, you can cover it by a couple of tests and be sure that it will stay up-to-date in future.</p><p><strong>💚 Trust.</strong> If you’ve got some users on your website, you know how important it is to keep them happy. Users trust our apps when they give us their personal data and money, or spend their time on our website, or recommend it to a friend. <a href="http://joelhooks.com/blog/2018/10/02/ive-got-a-confession-to-make/">When that trust is broken, it is so hard to regain.</a> By investing in automated testing you make a huge step towards building and retaining users’ trust.</p><p>I most likely missed a dozen of other good points for this list, so please feel free to share your own reasons for writing tests. I’m sure that in the end we will get a long list of benefits. That’s why I say that automated tests are awesome.</p><p><strong>With all these benefits in mind, why automated testing is not widely adopted in web development?</strong></p><p>Again, there is a number of reasons for it:</p><p><strong>🤬 Learning curve.</strong> There are plenty of tools, services, articles and books which often communicate contradictory messages about testing. It takes time to understand key concepts and to figure out that there is no one “right” way.</p><p><strong>🤬 Unit tests are overrated.</strong> There are many tutorials and trainings which touch on basics of automated testing. Most of them don’t go far beyond a trivial unit test example. As a result, developers start associating automated testing with unit tests only. In fact, automated testing tools are much more diverse and powerful than just unit tests and it’s unfortunate that developers keep focusing on unit tests only.</p><p><strong>🤬 Continuous Integration (CI)</strong>. Please feel free to argue with me, but I strongly believe that CI setup is a prerequisite for automated testing. Sometimes it stops developers who didn’t have DevOps experience in the past. The good news is that modern CI tools are very easy to get started with. At SystemSeed, we have no sysadmins in the team because developers can configure CI without any advanced knowledge.</p><p><strong>🤬 False economy</strong>. And last but not least, there is always an attempt to save time by not investing in automation. As I mentioned above, in fact, automated testing helps reducing costs in the long run, but at the beginning it may look like the opposite.</p><p>In these blog post series I’m going to structure and share literally everything I’ve learned about the topic since I joined SystemSeed in 2015. We will start with high level overview and then dive into specific tools and techniques which we at SystemSeed use on every day basis.</p><p>Stay tuned and remember: automated tests are awesome!</p><h4>💌 P.S. If you liked the article please visit <a href="https://systemseed.com/">SystemSeed.com</a> and meet the team! If you want to know how else we use tools and tech to better serve our clients email me at <a href="/service/mailto:info@systemseed.com">info@systemseed.com</a>!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6560146c06e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/systemseed/testing-modern-web-apps-part-0-6560146c06e6">Testing modern web apps, Part 0: Automated tests are awesome</a> was originally published in <a href="https://medium.com/systemseed">SystemSeed</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>