Software testing junit tutorials and videos

Selenium-Jupiter: Selenium Tests with JUnit

Software Testing Magazine — Mon, 11 Jan 2021 13:26:17 +0000

Selenium is a widely used open source framework for end-to-end web testing nowadays. JUnit 5 is the latest version of this popular Java open source unit testing framework and implements a brand-new programming and extension model named Jupiter. This talk presents Selenium-Jupiter. This is an open-source JUnit 5 extension that provides seamless integration with Selenium. It allows creating Selenium tests using local or remote browsers, reducing the required boilerplate thanks to the dependency injection mechanism supported in JUnit 5. Moreover, it will enable us to use different types of web browsers and Android devices in Docker containers out of the box. All in all, Selenium-Jupiter can be used to carry out different types of tests for web and mobile applications, including functional, compatibility (using test templates to define different devices or browsers -types and versions-) or performance (using a significant number of browsers through Kubernetes) tests. Selenium-Jupiter provides also advance capabilities for diagnostics, i.e., finding the root cause of a failed Selenium test. The first one is screenshotting. When a failure is detected, the state of the browser just before the failure happens can provide the clue to determine the nature of the problem. If the screenshot is not enough, the next step is to watch the browser during the test to observe the evolution of the web under test. This process is straightforward when running a test with the local browser, but it can be tricky in the usual case of running a test in a headless environment, such [...]

The post Selenium-Jupiter: Selenium Tests with JUnit first appeared on Software Testing Magazine.

Integration & End-to-End Testing with TestContainers and JUnit 5

Software Testing Magazine — Mon, 09 Dec 2019 16:16:08 +0000

The TestContainers library facilitates simple start up of a service dependencies, i.e. Postgres, Redis in throwaway Docker containers. This open source library works over Docker API and has a list of features which significantly improve a software developer experience. Some of these features are: * Docker environment autodiscovery * mapping to random unique host ports * easy Docker network configuration and sharing * waiting strategies for a ready status – containers cleanup guarantees * ready to use specific containers * JUnit 5 integration This talk discusses the above-mentioned features with code samples. The demo part shows integration tests for two services. They use Postgres and Redis under the hood, respectively. Another demo shows how it is possible to run both of the services in Docker containers at the same time together with their dependencies and to perform a simple end-to-end test. Video producer: https://voxxeddays.com/

The post Integration & End-to-End Testing with TestContainers and JUnit 5 first appeared on Software Testing Magazine.

Junit5: The Next Gen of Android Testing

Software Testing Magazine — Mon, 24 Jun 2019 13:56:21 +0000

Junit 5 is a big step for the world of unit testing for Android apps. This is a new very flexible open source testing framework, based on many years of experiences with Junit 4. At the sporttotal company, we use Junit 5 for our Android unit tests and it changed the way we write our tests. Hard for us to imagine living without features like @Nested. Other features we ignored as those are more leaning towards Java and are solved already by Kotlin or other Kotlin libraries. And some features are even breaking changes. How do you test on Android in a world without TestRunner and TestRules? Android testing team was always very slowly in adopting to new Junit versions, so how far can we bypass this? This presentation do a deep dive into Junit5, how it works and how we can use it to test our Android application. https://www.youtube.com/watch?v=5fIkkoPtPaw Video producer: http://droidcon.nyc

The post Junit5: The Next Gen of Android Testing first appeared on Software Testing Magazine.

Java Unit Testing: Spock versus JUnit 5

Software Testing Magazine — Mon, 25 Mar 2019 16:04:55 +0000

Spock was a game changer for all the Java software developers struggling with unit testing in JUnit 4. Compact syntax, parameterized tests or flexibility to mention just a few advantages. Over 10 years after JUnit 4.0, the brand new, written from scratch, Java 8 optimized JUnit 5 has been released. Is it still worth to write tests in Spock? This presentation compares selected areas of Spock and JUnit 5 to give you an overview how the situation looks like in 2018. It tries to answer the question if its time for Spock to fade into oblivion or maybe quite the opposite it is still light years ahead of JUnit 5. Video producer: http://www.jfokus.com

The post Java Unit Testing: Spock versus JUnit 5 first appeared on Software Testing Magazine.

Testing on the JVM with JUnit5

Software Testing Magazine — Mon, 04 Dec 2017 14:13:13 +0000

JUnit 5 is the next generation of JUnit. The goal is to create an up-to-date foundation for developer-side testing on the JVM. This includes focusing on Java 8 and above, as well as enabling many different styles of testing. JUnit 5 is now composed of the JUnit Platform, JUnit Jupiter and JUnit Vintage. The JUnit Platform serves as a foundation for launching testing frameworks on the JVM. It also defines the TestEngine API for developing a testing framework that runs on the platform. Furthermore, the platform provides a Console Launcher to launch the platform from the command line and build plugins for Gradle and Maven as well as a JUnit 4 based Runner for running any TestEngine on the platform. JUnit Jupiter is the combination of the new programming model and extension model for writing tests and extensions in JUnit 5. The Jupiter sub-project provides a TestEngine for running Jupiter based tests on the platform. JUnit Vintage provides a TestEngine for running JUnit 3 and JUnit 4 based tests on the platform. This video starts with an overview of the inspiration for and architecture of JUnit 5, from launchers to test engines, and then takes the audience on a live coding tour, covering support for tagging, custom display names, dependency injection, repeated tests, parameterized tests, conditional test execution, lambda expressions for assertions, assumptions, dynamic tests, and implementing tests via interface default methods (a.k.a., testing traits). The presentation goes over the extension model in JUnit Jupiter, discussing how to author and [...]

The post Testing on the JVM with JUnit5 first appeared on Software Testing Magazine.

An Overview of JUnit 5

Software Testing Magazine — Mon, 29 May 2017 15:15:36 +0000

JUnit 5 is the next generation of JUnit. The goal of this upcoming version is to create an up-to-date foundation for developer-side testing on the JVM. The evolution includes focusing on Java 8 and above, as well as enabling many different styles of testing. In his article, Nicolai Parlog explains how you should write tests with JUnit 5. After explaining how JUnit 5 should be setup, the article starts with some examples of the new Java unit tests written with JUnit 5: classic assertions, extended assertions or nesting tests. Then he explains the concept of dynamic tests that allows to define tests at run time. He also describes the JUnit 5 extension model, which defines a list extension points like Test Instance Post Processor, BeforeAll Callback or Test & Container Execution Condition. In his conclusion, he mentions that “JUnit 5 isolates “JUnit the platform” from “JUnit the tool” by implementing a clear separation of concerns and splitting itself into three subprojects.” This separation between JUnit Jupiter and JUnit Platform means that JUnit Jupiter can evolve without tools depending on some implementation details, as it was the case with the previous versions of JUnit. Read the complete article on https://jaxlondon.com/blog/junit-5-next-generation-testing-on-the-jvm/

The post An Overview of JUnit 5 first appeared on Software Testing Magazine.

Testing Microservices

Software Testing Magazine — Tue, 30 Aug 2016 08:55:07 +0000

The microservice architecture has been growing momentum over the past few years in the Java world, but once you have started down the microservice path how do you make sure that your applications are still fully tested? This presentation provides an overview of the trials and tribulations when testing microservices. It will cover the different testing types that are required, using a sample java-based microservice to highlight the reasons for the requirements. It will also reference this sample microservice as an example of some of the testing techniques that can be used. These techniques will include testing microservices with a Gradle or Maven build system and using testing tools such as JUnit. Video producer: http://www.jfokus.com

The post Testing Microservices first appeared on Software Testing Magazine.

Replacing Rules in JUnit 5

Software Testing Magazine — Tue, 17 May 2016 16:26:02 +0000

Rules have disappeared in the version 5 of the JUnit open source Java testing tools. The release 5 of JUnit is still in alpha status. In this article, Herrmann Rüdiger explores what it would take to transform existing rules to the new concept so that they could run natively on JUnit 5. The article starts by explaining extensions, a new concept in JUnit. These extensions will be a good way to replace rules in JUnit and the blog post provides many code examples on how to achieve this goal. An interesting new features is that JUnit 5 provides a means to maintain state of extensions called Stores. Stores provide methods for extensions to save and retrieve data. The conclusion of the blog post is “extensions are a decent and complete replacement for rules and friends in JUnit 4. And finally, using the new methods is fun and feels much more concise than the existing facilities. […] But note however, that as of this writing extensions are work in progress. The API is marked as experimental and may change without prior notice. Thus it might be a bit early to actually migrate your JUnit 4 helpers right now – unless you don’t mind to adjust your code to the potentially changing APIs.” Read the full blog post on http://www.codeaffine.com/2016/04/06/replace-rules-in-junit5/

The post Replacing Rules in JUnit 5 first appeared on Software Testing Magazine.