Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a testing environment for Pairing Bot #23

Open
stillgreenmoss opened this issue Jun 24, 2021 · 3 comments · Fixed by #64
Open

Create a testing environment for Pairing Bot #23

stillgreenmoss opened this issue Jun 24, 2021 · 3 comments · Fixed by #64
Assignees
Labels
enhancement New feature or request

Comments

@stillgreenmoss
Copy link
Collaborator

Pairing Bot does not currently have a testing environment -- it would be awesome if she did!

Any recurser, though especially recursers currently in batch, should message me or @parsn1psoup if they'd like to work on this.

@cceckman
Copy link
Collaborator

@stillgreenmoss Does the -dev environment / testing version satisfy this?

@cceckman cceckman added the enhancement New feature or request label Aug 6, 2024
@cceckman
Copy link
Collaborator

cceckman commented Aug 6, 2024

The "dev" environment is pretty usable for this. It has the crons (which can be triggered manually), has its own database and bot-user, so it can do most end-to-end things without bothering non-developers. (It won't send the broadcast messages, e.g. end-of-batch or weekly checkins, so those are a bit harder to test.)

@jdkaplan mentioned doing some work on allowing Pairing Bot to run locally, which I think would be a nice enhancement to the test-ability; it's a pain to wait multiple minutes for a GAE build, when the program itself takes a fraction of a second to build.

@jdkaplan
Copy link
Collaborator

jdkaplan commented Aug 6, 2024

I think I've got something! There's a Firestore emulator available as an optional gcloud component, which is well-supported by the Firestore SDK we're using. I've got a proof-of-concept DB round-trip test that runs entirely locally!

I'm fairly certain that I can get it running in CI by using the official setup-gcloud action.

I'll have a draft PR up in a bit to iterate on the CI setup and make sure the local dev stuff is portable to other machines.

@jdkaplan jdkaplan self-assigned this Aug 6, 2024
@jdkaplan jdkaplan linked a pull request Aug 6, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants