PrimeFaces VS junit5

> I use Quasar and Vue. This is my hammer for all nails, no matter the size of the nail.

Vue is great, especially with their Composition API (https://vuejs.org/guide/extras/composition-api-faq.html#why-...) and something like Pinia for state management, without the hassles of something like Redux: https://pinia.vuejs.org/

As for components, I really liked the idea behind PrimeVue/PrimeReact/PrimeNG/PrimeFaces (https://www.primefaces.org/) because I'm not aware of any other attempts of creating components that actually work similarly across different frameworks/libraries and it's really good because your skills carry over pretty well if you ever find yourself exploring a slightly different stack.

For what it's worth, the components also work decently (there's a whole list https://primevue.org/autocomplete/) and look okay (with various themes available, https://primevue.org/theming/), plus you can get examples (https://blocks.primevue.org/). Oh yeah, they also have their CSS utilities (a bit like Tailwind, https://primeflex.org/installation) and icons (https://primevue.org/icons).

I actually look forwards to the day where most of these concerns are less of an artisanal craft but rather a set of boring and well known things that just work well for quickly putting together a CRUD or whatever you need.

That said, I also explored VueRequest for handling network requests a bit more easily (https://www.attojs.org/guide/gettingStarted.html) and VueUse for stuff like LocalStorage (https://vueuse.org/guide/) and while it doesn't feel like I'm building a crappy alternative to Vuex and the complexity is reasonably manageable and the usability present, occasionally it all still feels a bit annoying to deal with - reactivity, ways to shuffle around data that I get from the back end, props, various bugs... so it's not all good, but still less complex than some of the things I've seen with React or Angular.

Visit the changelog for the complete list of changes.

Used this years ago for JSF apps https://www.primefaces.org/ I know they've kept it updated for current angular/react/vue JS front ends, but I've never used those. Might be worth a look.

It might be related to this

PrimeFaces (PrimeFaces official page has implementations for Angular, React and Vue)

> I'd like to hear any strategy one has to deal with that. I have taken up Figma and Sketch so I can meet them "where they are" but still, plenty of disagreements can happen.

One option would be to use a premade design system or a component library/framework that gives you a consistent look and feel, most of those design decisions having a good enough baseline. Then just add a color theme and some branding on top of it and call it a day. It will also increase your development velocity and save you from some pixel pushing.

For an example of this, consider PrimeFaces: https://www.primefaces.org/

They have working components that are good enough (and support multiple themes, if need be), their own icon solution and also a CSS utility library, including stuff like layouts. For most projects it'll be enough to create something that works and looks okay.

> A UI library for React, Vue, Svelte, Solid, whatever... Imagine being able to have a component library that works with any of them (or none of them).

That seems to be a worthy goal, but I don't see that being usable in prod projects, at least not in the near future.

The closest I've seen is something like PrimeFaces, which has components for Angular, React and Vue, which is the majority of projects I've seen out there: https://www.primefaces.org (I've also used the Java JSF variety, it was... sometimes problematic)

If you need something that works the same (or as close as you can get) across multiple front end frameworks/libraries, while still having most of the components you could possibly want, I don't think there are many other options out there.

For example:

- Angular calendar: https://www.primefaces.org/primeng/calendar

- React calendar: https://www.primefaces.org/primereact/calendar/

- Vue calendar: https://www.primefaces.org/primevue/calendar

I liked Prime ( https://www.primefaces.org/ )

To make the above check work we need to wrap it in JUnit test:

Java / JUnit

Next, you need to install a testing framework that will be used for performing unit testing in your project. Several testing frameworks are available depending on the programming language used to create an application. For example, JUnit is commonly used for Java apps, pytest for Python apps, NUnit for .NET apps, Jest for JavaScript apps, and so on. We’ll use the Jest framework for this tutorial since we are using JavaScript.

This repository provides a BuildImageTest that uses the buildpack to create a native image. It then tests the native image, using Testcontainers and JUnit. Building the native image with AOT processing, as part of a test, takes minutes not seconds, and should not be part of normal "inner loop" development. So the BuildImageTest is in a separate sourceSet and can be executed independently. This is a very powerful pattern, that I'm just getting started with. I would love to hear your thoughts on this pattern or other alternatives to it.

To get started with testing, search for a popular testing framework for your programming language. PHP has PHPUnit, for example. Java has JUnit. Flutter apps use Flutter Driver. No matter your language or framework, there is a testing framework that will work for your app.

Another library which may be of use to you once you've gotten to grips with the basics of Java is JUnit. JUnit provides functionality for unit testing, allowing you to more easily see if your code is working as expected/if you've accidentally broken anything, via letting you write tests that can check if your code is behaving as expected or not.

Official Website : https://junit.org/

In my last episode (https://youtu.be/cs2Wu9Co-2s) I said that we shouldn't use JUnit @BeforeEach to setUp test fields. Christoph Sturm (https://twitter.com/globalo) pointed out that there is an, erm, feature of JUnit 5 that means that we sometimes have to use @BeforeEach methods to initialise resources if we want them to be released in @AfterEach. The bug report is here https://github.com/junit-team/junit5/issues/1358 With or without this feature, we probably should use @BeforeEach to run code that will allocate non-memory resources that we need to free in @AfterEach, if only for symmetry. I suppose that also applies to any side-effects that we need to be reverted and that are not confined to the state of the test fixture.

Testing tools on the JVM stopped using reflection about twenty years ago, they all use annotations these days (e.g. https://testng.org, https://junit.org). Rust has annotations too, obviously.

Testcontainers is a Java library that supports JUnit tests providing lightweight instances of anything that we can run in a Docker container.