<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Unit Testing on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/unit-testing/</link><description>Recent content in Unit Testing on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 21 Oct 2024 14:00:53 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/unit-testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Unit Testing Web Frontend For Accessibility Aspect</title><link>https://javapro-en.svenruppert.com/unit-testing-web-frontend-for-accessibility-aspect/</link><pubDate>Mon, 21 Oct 2024 14:00:53 +0000</pubDate><guid>https://javapro-en.svenruppert.com/unit-testing-web-frontend-for-accessibility-aspect/</guid><description>&lt;p&gt;&lt;figure class="post-figure"&gt;
 &lt;img src="https://javapro-en.svenruppert.com/uploads/2024/10/image-1.jpeg" alt="" loading="lazy" decoding="async"&gt;
 
 
 
&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;&amp;ldquo;&lt;a href="https://www.flickr.com/photos/136485307@N06/48286447167"&gt;Apollo 11 Altitude Chamber Test&lt;/a&gt;&amp;rdquo; by &lt;a href="https://www.flickr.com/photos/136485307@N06"&gt;Apollo Image Gallery&lt;/a&gt;/ &lt;a href="https://creativecommons.org/publicdomain/mark/1.0/?ref=openverse"&gt;pdm 1.0&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When we’re talking about unit testing, it is something that developers want to avoid, but what about accessibility?? the same thing, even most developers will say, ‘Nah, I&amp;rsquo;m good` *kidding&lt;/p&gt;
&lt;p&gt;So, what is unit testing?? Isn’t it enough when we test the feature we developed works fine? The short answer may not be! I’ll tell you why&amp;hellip;&lt;/p&gt;
&lt;p&gt;Unit testing is a way of testing a unit — the smallest piece of code that can be logically isolated in a system. In most programming languages, that is a function, a subroutine, a method, or a property. The isolated part of the definition is important. In his book “Working Effectively with Legacy Code”, author Michael Feathers states that such tests are not unit tests when they rely on external systems: “If it talks to the database, it talks across the network, it touches the file system, it requires system configuration, or it can’t be run at the same time as any other test.”Modern versions of unit testing can be found in frameworks like JUnit, or testing tools like &lt;a href="https://smartbear.com/product/testcomplete/overview/"&gt;TestComplete&lt;/a&gt;. Look a little further and you will find SUnit, the mother of all unit testing frameworks created by Kent Beck, and a reference in chapter 5 of The Art of Software Testing. Before that, it was mostly a mystery. I asked Jerry Weinberg about his experiences with unit testing — “We did unit testing in 1956. As far as I knew, it was always done, as long as there were computers”.Regardless of when and where unit testing began, one thing is for sure. Unit testing is here to stay. Let’s look at some more practical aspects of unit testing. In fact, the traditional test of our application by black box testing, the thing that we talked about earlier manual testing only finds whether the feature that we developed already works or not. Then, when we talk about something important thing that most developers skip or miss is about accessibility (a11y). Accessibility is when we design, and develop products and any application that we put on it our thoughts about how this thing will work for everyone literally everyone, diversity disabilities included. So when we combine both a11y and unit testing it will lead to perfection.&lt;/p&gt;</description></item></channel></rss>