testing-library-docs VS mantine

Testing Library provides a great set of accessibility-focused tools to locating elements when writing tests. It was created by Kent C Dodds, one of my longtime favorite educators on front-end and testing topics. Since the initial release in 2018 as "React Testing Library", it's grown in popularity beyond its React component testing roots. It now has plugins for all major test runners and JavaScript frameworks, and in 2022 some of its patterns were adopted in Playwright's test runner as the recommended way to locate elements.

Probably Enzyme was the first to popularize component testing in React by doing shallow rendering and expecting some things to be there in the React component tree. Then React Testing library came and took component testing to a whole new level.

18.react-testing-library

Jest has long been my favorite got to test runner when it comes to UI unit and integration testing. With tools like React Testing Library (Testing Library framework for React) you get the benefit of very easy to write and maintain tests, as well as a quick and efficient way to run our tests.

I'm writing an intergration test with Testing Library where I'm on a boards dashboard area and a user can click a button to create an item on the board. I'm using an intercepting route to do show the popup form. Once finished the user goes back to their area and should see the created board.

This article uses Jest and React Testing Library. It's okay if you want to use other libraries, the fundamentals in this article will help you there as well.

This is the idea behind Testing-Library from what I understand.

https://testing-library.com/

The Testing Library: The Testing Library offers guidance on best practices for testing user interfaces effectively, with a focus on user-centric testing.

There are great tools like Testing Library that render a single component in a single state and then programmatically inspect the resulting DOM. However, the salient details of the rendered HTML – like color, layout, and scale – are hard to express. So, the tests end up brittle (over-specified) or insufficient (under-specified).

Here’s another mentality shift for you. If you were thinking in a providers pattern, you need to snap out of it. You can no longer store your theme in a provider. No more RadixUI or MantineUI for you.

import { TextInput, Select } from '@mantine/core'; // Example usage ; ; Enter fullscreen mode Exit fullscreen mode Maps: React Simple Maps provides maps that are valuable for visualizing geospatial data. You can integrate interactive maps into your dashboard to represent data points geographically. import {ComposableMap, Geographies, Geography, Marker} from "react-simple-maps"; // Example usage {...} {... return ( ); })} Enter fullscreen mode Exit fullscreen mode By incorporating these core components, our template accelerates the development of admin dashboards. These components are designed to work seamlessly together, providing a cohesive user experience. You can effortlessly create complex data visualizations, interactive tables, intuitive forms, and interactive maps — essential elements that transform raw data into meaningful insights. Deploying the Template to a Live Environment Deploying our admin dashboard template to a live environment is a straightforward process. We recommend utilizing popular hosting platforms like Vercel, Netlify, or Firebase Hosting. These platforms offer seamless integration with Next.js and allow you to deploy with a few simple steps: Install Required Dependencies: Ensure you have the necessary dependencies specified in the package.json file. Build the Project: Generate a production build of your Next.js application using the command: npm run build. Select Hosting Platform: Choose your preferred hosting platform (e.g., Vercel). Connect Repository: Link your template’s GitHub repository to the hosting platform. Configure Deployment Settings: Configure deployment settings, such as branch selection and build commands. Deploy: Trigger the deployment process. The hosting platform will automatically build and deploy your admin dashboard template. Real-World Use Cases The versatility of our admin dashboard template knows no bounds. It caters to a myriad of real-world use cases, each tailored to specific industries and applications: E-Commerce Management: The template can be employed to manage product listings, order processing, and inventory tracking for online stores. Data Analytics: With its data visualization components, the template can serve as a dashboard for analyzing metrics, trends, and insights. Project Management: The template’s customizable components facilitate the creation of project management tools for tracking tasks, deadlines, and team collaboration. SaaS Applications: As the foundation of a Software as a Service (SaaS) application, the template streamlines user management, subscription tracking, and data presentation. Content Management: It can also function as a content management system dashboard, offering tools to manage articles, media, and user-generated content. Live Demo For a hands-on experience, explore the live demo of our admin dashboard template: Live demo — https://mantine-analytics-dashboard.netlify.app/ Witness the template’s adaptability, responsiveness, and functionality firsthand. Feel free to interact with its components, navigate through its sections, and envisage how it could seamlessly integrate into your projects. Contributing and Support I welcome all developers and enthusiasts to contribute to the growth of our open-source admin dashboard template. Contributing is a collaborative process that empowers us to collectively enhance the template’s capabilities and quality. To get started: Fork the Repository: Fork the template’s GitHub repository to your own GitHub account. Clone the Fork: Clone the forked repository to your local machine using Git. Create a Branch: Create a new branch for your contributions to keep the main codebase intact. Implement Changes: Make your desired changes, add new components, or refine existing features. Commit and Push: Commit your changes to the new branch and push them to your GitHub fork. Submit a Pull Request: Submit a pull request from your forked repository to the main template repository. Your changes will be reviewed and potentially merged. Conclusion In summary, our Mantine and Next.js admin dashboard template offers a range of benefits that empower developers, designers, and entrepreneurs to create exceptional admin interfaces: Efficiency and Speed: The template expedites development by providing a pre-built foundation of components and features, allowing you to focus on customization and innovation. Consistency and Aesthetics: Mantine’s design-first approach and Next.js’s performance optimizations ensure a consistent and visually appealing user experience. Flexibility and Customization: The template’s modularity and theming options facilitate easy customization to align with your project’s unique branding and requirements. Rich Functionality: The integration of core components such as charts, tables, forms, and maps equips you with tools to tackle diverse dashboard functionalities. Invitation to Explore and Utilize The Mantine and Next.js admin dashboard template isn’t just an end; it’s a beginning — a starting point for your creative journey. Whether you’re a seasoned developer seeking a rapid launch or an enthusiast keen on learning modern development practices, this template is your canvas. Additional Resources GitHub repository — https://github.com/design-sparx/mantine-analytics-dashboard Mantine — https://mantine.dev/ Nextjs — https://nextjs.org/ Code documentation — https://mantine-analytics-dashboard-docs.netlify.app/

While I have experience with Tailwind and frontend development, I don’t really have the patience to use it. I usually end up using something like Mantine, which is a complete component library UI kit, or Daisy UI, which is a component library built on top of Tailwind. Shadcn/ui is quite similar to Daisy in this sense, but being able to customize the individual components, since they get installed to your components folder, made development more streamlined and more customizable. On top of that being able to change my components style with natural language thanks to v0 made development super easy and fast. Shadcn may be too minimalist of a style for some, but thanks to all the components being local, you can customize them quickly and easily!

Great compilation. Thanks for putting that together.

Curious what your take is on these UI libraries that "claim" they are accessible:

https://mantine.dev - "Build fully functional accessible web applications faster than ever"

29.react-mantine

I am currently using mantine.dev , and i am very happy with the results, i haven't done any customization, if you want to give a look on my website: https://culturadocaractere.com.br

GitHub stars: 21.9k GitHub link: https://github.com/mantinedev/mantine Documentation: https://mantine.dev/getting-started/