Refract
  • Read Me
  • Introduction
    • Why Refract?
    • Core Concepts
    • Thinking In Refract
    • Alternatives
  • Usage
    • Getting Started
    • Installation
    • Connecting To React
    • Observing React, Preact and Inferno
    • Injecting Dependencies
    • Observing Redux
    • Observing Anything
    • Handling Effects
    • Pushing to Props
    • Rendering Components
    • Handling Errors
    • Testing
  • Recipes
    • Dependency Injection
    • Creating An API Dependency
    • Handling state
    • Replacing Redux Connect
  • Examples
    • Debounced fetch
    • Counter
    • Field validation
    • Redux fetch
    • Routing
    • Typeahead
    • Visit time
  • API
    • compose
    • withEffects
    • toProps, asProps
    • useRefract
    • refractEnhancer (Redux)
  • Glossary
  • Feedback
Powered by GitBook
On this page
  1. Usage

Testing

PreviousHandling ErrorsNextRecipes

Last updated 6 years ago

Refract's API has been designed so that each facet (aperture, handler, errorHandler) is pure, which means they can be tested in isolation.

How you test the internals of your aperture depends on which streaming library you choose, as they all offer different testing approaches. We would like to compile a list of useful links on testing for each of the streaming libraries integrated with Refract, so if you encounter any please either open a PR or get in touch via !

our Discord channel