Skip to content

Improving Integration Test Start Time #277

Description

@pconrad

Following the example of ucsb-cs156/proj-frontiers#649, change the pom.xml so that integration tests start faster.

Here is the desired behavior, adapted from that PR by @Division7

Improve the start time for integration tests by further granularizing when maven attempts to reinstall the node, npm, and the project's frontend dependencies.

Specifically: If package-lock.json or package.json are newer than the last time the project was copied to the build directory, maven should attempt to reinstall npm, node, and run npm install.

Also: If the dependencies changed, or the frontend code changes, maven will rebuild the project and re-copy it to the directory.

As a result, maven no longer needs to run npm ci every single time you make a code change to the frontend while attempting to work with integration tests.

Metadata

Metadata

Assignees

No one assigned

    Labels

    S26follow-the-leaderTake code from a PR in another project; apply those changes here. Often easy, sometimes hard.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions