test PR to replicate issue #1775

[ajvs]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Related Issue

Example: #1775

Describe this PR

A brief description of how this solves the issue.

Screenshots

Please provide screenshots of the change.

Alternative Approaches Considered

Did you attempt any other approaches that are not documented in code?

Review Guide

Notes for the reviewer. How to test this change?

Checklist before requesting a review

• 📖 Read the Field-TM Contributing Guide: https://github.com/hotosm/fmtm/blob/main/CONTRIBUTING.md
• 📖 Read the HOT Code of Conduct: https://docs.hotosm.org/code-of-conduct
• 👷‍♀️ Create small PRs. In most cases, this will be possible.
• ✅ Provide tests for your changes.
• 📝 Use descriptive commit messages.
• 📗 Update any related documentation and include any relevant screenshots.

[optional] What gif best describes this PR or how it makes you feel?

[spwoodcock]

All the tests are currently skipped, so you will need to enable them again I think 😄

Good news is the test runs and gets this far though! So if they fail when the tests are enabled, we can confirm its either:

• Lack of access to the environment called 'test' to use the variables (from forked repos)
• An issue with playwright or the tests (less likely)

I have a feeling we need a way to make the test environment in Github accessible from forked repos - low risk, as that environment contains no secrets

[spwoodcock]

Running now! I disabled the approval requirement on workflows from new contributors 👍

[spwoodcock]

I think this was healthcheck issue you mentioned 👍

[ajvs]

That did resolve the healthcheck issue, @spwoodcock.
I enabled the tests to check if they will work, but unfortunately they still fail. maybe the tests don't match the code in this branch?
Anyway, not sure if this is still related to the forked repo issue we were originally looking into.

[spwoodcock]

Yeah perhaps not 😅

We disabled the e2e tests a while ago, after the issue regarding forked repos was made, so it's hard to address this issue without first re-enabling the e2e tests and ensuring they work first - sorry!

(the reason the e2e tests were disabled is simply due to lack of capacity / time)

[ajvs]

no worries. :)
I'll work on another issue for now.