Test/base example

[zacdezgeo]

What I Changed

• Moved plugin code and related assets to ee_plugin folder (mainly to solve import errors for our tests)
• Add base example in readme to an automated test under test/test_map.py
• Update other asset paths in other tests
• Update CI

How to Test It

• Verify Github Action execution
• Run tests locally (python -m pytest test)
• Spin up QGIS and run base example

Other Notes

• Closes Error after layer is added  #195 via Bug 195/add vector layer #196
• Though not extensive, we setup most of the line items in Increase Code Coverage for Existing Plugin Functionality  #179. We should continue adding tests to features we change or add, but this closes Increase Code Coverage for Existing Plugin Functionality  #179.

[zacdezgeo]

@gena; the tests currently fail because of authentication (see the github run here). We need to add secrets.EE_CREDENTIALS_JSON to our GitHub secrets. The refresh token doesn't expire, so this should be a lasting solution. @alukach and I do not have admin or maintainer rights, so we can't add the secret.

We did some due diligence to ensure the packaging matches the previous structure even with our refactoring, but we might have some blindspots in how things are published. From our research into the packaging CI and the pavement.py package task, we should have covered everything needed.

[zacdezgeo]

We added our EE credentials to the secrets and the tests now pass. We flagged some future improvements on the CI that can be addressed at a later time. They mostly have the intent of optimizing the run (time):

• Add Python Version Matrix Testing to CI #193
• Optimize CI with a Custom Docker Image for QGIS Dependencies #192
• Add Python Setup with Dependency Caching to GitHub Actions #191

[alukach]

I don't love hardcoding these paths into our repo but I think we can refine that later. These are simply for developer experience so will just be an annoyance for any plugin developers with differing paths.