Skip to content

When developing, it is difficult to run a single test spec #1016

Closed

Description

@KevinEady

Running npm test will re-compile all files as it uses node-gyp rebuild. We can simplify this to compile only modified files by using node-gyp build -- however, modifying the napi[-inl].h file will consider all test specs as modified.

It would be helpful if we could have some way to compile + run only one test spec, such that only the relevant .cc file for that spec (as well as the overall binding) are compiled.

Activity

  1. deepakrkris commented on Jul 2, 2021

    @deepakrkris
    Contributor

    I am working on this story

  2. github-actions commented on Oct 1, 2021

    @github-actions
    Contributor

    This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

  3. github-actions commented on Jan 11, 2022

    @github-actions
    Contributor

    This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

  4. github-actions commented on May 4, 2022

    @github-actions
    Contributor

    This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

  5. deepakrkris commented on May 5, 2022

    @deepakrkris
    Contributor

    @KevinEady @mhdawson I believe this can be closed for now, since we had some work on this and merged a PR

  6. mhdawson commented on May 6, 2022

    @mhdawson
    Member

    @deepakrkris the only question I have is if how to run a single test is documented somewhere? If so could you add the link here and then I think we can close.

  7. deepakrkris commented on Aug 12, 2022

    @deepakrkris
    Contributor

    @mhdawson I think that is not documented. let me bring this up in our weekly meeting today. I can add in a readme or in a wiki

  8. mhdawson commented on Aug 17, 2022

    @mhdawson
    Member

    @deepakrkris thanks, I think adding to the Readme would be a good way to go. I was out last week but will be there this week.

  9. deepakrkris commented on Aug 19, 2022

    @deepakrkris
    Contributor

    @mhdawson doc PR : #1199

  10. mhdawson commented on Aug 19, 2022

    @mhdawson
    Member

    @deepakrkris thanks landed that PR closing this. Many thanks for your work on making testing easier.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions