react-testing-library VS Made With ARKit

• Focused on user-centric testing
  React Testing Library encourages tests that closely resemble how users interact with an application. This approach makes tests more reliable and meaningful.
• Reduces coupling to implementation details
  By encouraging developers to interact with components via the DOM, the library minimizes dependencies on component internals, making tests less prone to breaking from refactors.
• Improved test readability
  Tests written with React Testing Library are generally easier to read and understand because they focus on what the user sees and does, rather than the internal logic of the components.
• Comprehensive query options
  The library provides a wide range of query methods (e.g., getByText, getByRole), which makes it easy to select elements in ways that resemble how users think.
• Active community and well-maintained
  React Testing Library has a strong, active community and it's maintained by experienced developers who keep the library up-to-date with React's evolution.

Possible disadvantages

• Limited support for non-DOM testing
  The library is heavily focused on DOM interactions, making it less suited for testing non-DOM logic or scenarios that don't involve user interactions.
• Can be slower
  Tests that involve the DOM can be slower compared to tests that interact directly with component methods and state, which can lead to longer test execution times.
• Learning curve for traditional testers
  Developers who are used to testing implementation details with other tools (like Enzyme) might find it challenging to adjust to the user-centric approach advocated by React Testing Library.
• Potential for less granular control
  Because the library encourages testing through the UI, developers might find it harder to test specific, isolated internal behaviors of components that aren't directly visible to users.
• Dependencies on browser APIs
  The library's reliance on browser APIs means that tests may behave differently in different environments or may require polyfills for certain features, leading to potential inconsistencies.

• Curated Content
  Made With ARKit showcases a curated collection of augmented reality (AR) applications and projects, which helps users discover high-quality AR experiences created with Apple's ARKit.
• Inspiration
  The platform can serve as a source of inspiration for developers and designers looking to see what’s possible with ARKit, sparking ideas for their own projects.
• Community Engagement
  Made With ARKit fosters a sense of community among AR developers, allowing them to share their work, gain feedback, and collaborate with others in the space.
• Visibility for Developers
  By being featured on Made With ARKit, developers can gain visibility for their projects, potentially attracting users, collaborators, or investors.
• Showcases ARKit's Potential
  The platform highlights the capabilities of Apple's ARKit, demonstrating the innovative and diverse range of applications that can be built using the technology.

Possible disadvantages

• Limited to ARKit
  Made With ARKit exclusively features projects created with Apple's ARKit, which may exclude or overlook compelling AR experiences built using other platforms or technologies.
• Curation Bias
  The curated nature of the platform means there could be a bias in which projects are featured, potentially overlooking smaller or independent developers’ work.
• Quality Control
  While curation aims to ensure quality, the subjective nature of what is deemed high-quality could result in a varied range of user experiences.
• Dependence on ARKit Updates
  The platform's relevance is tied to the continuous innovation and updates from Apple's ARKit. Any slowdown or issues with ARKit itself could impact the platform's content stream.
• Platform Dependency
  Developers who want visibility on Made With ARKit need to be developing specifically for the Apple ecosystem, which could limit their reach if they aim for cross-platform AR development.

React unit testing with Jest & React-testing-library

More videos

AR Restaurant Menu Concept made with ARKit

• Moving from Angular to React: A Practical Guide

  Testing Library. React Testing Library. https://testing-library.com/docs/react-testing-library/intro/. - Source: dev.to / 11 days ago

• Test-Driven Development for Building User Interfaces

  React Testing Library’s core philosophy is that we should write our tests in such a way that we simulate user behavior. By testing what the user can actually do, our tests focus less on implementation details and more on the actual user... - Source: dev.to / 8 months ago

• Chaos-Driven Testing for Full Stack Apps: Integration Tests That Break (and Heal)

  In the main branch, we set up Vitest as the test runner and React Testing Library for rendering the component and simulating user interactions. We also set up MSW to intercept the network requests and return mock responses. - Source: dev.to / about 1 year ago

View more

Tracking Made With ARKit since Mar 2021.