https://github.com/alexdlaird/air-quality-bot-e2e
E2E tests for the Air Quality Bot
https://github.com/alexdlaird/air-quality-bot-e2e
airquality aws-lambda bot e2e education python twilio twilio-sms
Last synced: 4 months ago
JSON representation
E2E tests for the Air Quality Bot
- Host: GitHub
- URL: https://github.com/alexdlaird/air-quality-bot-e2e
- Owner: alexdlaird
- License: mit
- Created: 2018-12-09T16:30:29.000Z (over 7 years ago)
- Default Branch: main
- Last Pushed: 2025-06-05T03:52:49.000Z (about 1 year ago)
- Last Synced: 2025-10-14T17:16:21.325Z (9 months ago)
- Topics: airquality, aws-lambda, bot, e2e, education, python, twilio, twilio-sms
- Language: Python
- Homepage: https://github.com/alexdlaird/air-quality-bot
- Size: 55.7 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README

[](https://github.com/alexdlaird/air-quality-bot-e2e/actions/workflows/ci.yml)
# Air Quality Bot E2E Tests
The [Air Quality Bot](https://github.com/alexdlaird/air-quality-bot) is
generally available by texting a zip code (and optionally the word "map") to
(415) 212-4229. This project runs end-to-end tests against the bot to ensure it
is up and responding properly.
## Running Locally
Run `make install`, then update the values in `.env` to reflect your account's
values. Ideally, E2E tests should run from against a different Twilio account
than the bot itself.
To run the tests, simply execute:
```sh
make test
```
## CI Build
For the E2E tests to run in a CI system, simply add the environment variables found
in `.env` to the configuration for the CI build. In the CI system, you can also
set these E2E tests to run based on a cron schedule.
In addition to running the E2E tests manually or on a schedule, you can trigger
them to run after each deploy. To do this, simply add the following variables to
your `.env` file in the [Air Quality Bot](https://github.com/alexdlaird/air-quality-bot/blob/main/.env.example)
repository. If they are set, E2E tests will automatically run after the
`./deploy.sh` script is executed successfully.