Skip to content
This repository was archived by the owner on Jun 10, 2019. It is now read-only.
This repository was archived by the owner on Jun 10, 2019. It is now read-only.

Create Jest snapshot tests of every shared component #327

Closed

Description

@rickr

Feature

Why is this feature being added?

See #326. We've chosen Jest as our unit testing library, and now we need to utilize it.

What should your feature do?

Integrate Jest
Create snapshot tests for every shared component
Make sure it runs in the build

Activity

  1. changed the title [-]Integrate Unit Test Framework[/-] [+]Create Jest snapshot tests of every shared component[/+] on Oct 1, 2017
  2. seeksort commented on Oct 7, 2017

    @seeksort

    Hello! Could I take on this one? This would be for all of the components in /src/shared/components, right?

  3. kylemh commented on Oct 7, 2017

    @kylemh
    Member

    @seeksort yes indeed! Wow, I was so excited to see this issue pop up in my notifications. You'll be integrating our first tests!!! I've assigned myself to this issue as a placeholder for you.

  4. self-assigned this
    on Oct 7, 2017
  5. seeksort commented on Oct 21, 2017

    @seeksort

    Still working on this, I've just been busy. I had a question though, what are everyone's thoughts on having a central __tests__ directory vs. a subdirectory in each component subfolder? Ryan Florence of React Router suggests having a separate__tests__ subdirectory for each component. I've seen it done both ways, though.

  6. kylemh commented on Oct 22, 2017

    @kylemh
    Member

    @seeksort no problem, as it seems you're the only person interested in helping with tests 😆

    I'm really not experienced enough to have an opinion on the matter. My first inclination is to stick with what people are most familiar with in a central __tests__ directory, since we work with many new developers. I see Ryan Florence's points, but what do you think?

  7. kylemh commented on Aug 22, 2018

    @kylemh
    Member

    Closing this issue in the spirit of preventing work on items that would not be implemented in the new repository. This is already implemented there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions