Versions Compared

Old Version 10

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version Current

changes.mady.by.user Hardy Pottinger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. These test instructions assume you are already running both the Frontend & Backend. If not, follow the instructions above, and then start them both:

    Code Block
    # Start backend
cd DSpace
docker-compose -p d7 up -d

# Start frontend
cd ../dspace-angular
docker-compose -p d7 -f docker/docker-compose.yml up -d


  2. Move into the directory where your Frontend code is:

    Code Block
    cd dspace-angular


  3. Find the number of the Pull Request you want to test (it'll be the "#[number]" displayed after the PR name, or the end of the PR's URL).  Checkout the code from that PR using it's number: 

    Code Block
    # This would checkout https://github.com/DSpace/dspace-angular/pull/1383 for testing
gh pr checkout 1383


  4. Now, rebuild & restart your frontend based on that PR's code:

    Code Block
    docker-compose -p d7 -f docker/docker-compose.yml up -d --build
# Even after the build completes, it makemay take a few minutes for the frontend to restart

# You can check the status using "logs -f"
docker-compose -p d7 -f docker/docker-compose.yml logs -f
# (Click Ctrl+C to exit logs view)


  5. Now test the User Interface to see if the changes made in that PR look to work properly.  The PR's description should describe how to test it and what you should see.
    1. If you notice any odd behavior, check for errors in the UI using your browser's DevTools. See Troubleshoot an error#FindingtheErrorMessageintheUserInterface
    2. Based on what you find, add a comment to the PR. If it works, congratulate the developer. If it doesn't, let them know the error you saw (and what you clicked on when that error occurred).

...