Create Test Environment

[hkatzdev]

Overview

We need to make a proper test environment to ensure that no changes break the production table.

Action Items

• Document all the current tables' schemas.
• Create a new table solely for testing.
• Implement schema into table.
• Add scripts / bots to run in the testing table.
• • Look into Library
• Add forms to allow test data.
• Populate the table with test data.
• • Add test drives
• • Add test calendar
• • Add test github
• remove the dependency on App Script Error Checking #12

Resources/Instructions

https://tables.area120.google.com/u/0/workspace/bHKoRlcCZyubeRsnie2OgH/table/aUgD85hZoYo2epgVPd4O1c
https://docs.google.com/spreadsheets/d/1kHsAi6jPpXaMpdr7YCBlJiePrzoNh6LSgDqvwO2_kec/edit
https://tables.area120.google.com/u/0/workspace/8JsRrAd7fEgd5jspaL4_qD/table/9gZ9xePJnfs2H65LCypkLZ
https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect

• email for staging tables-staging@hackforla.org

[hkatzdev]

An approximent schema is available at https://docs.google.com/spreadsheets/d/1kHsAi6jPpXaMpdr7YCBlJiePrzoNh6LSgDqvwO2_kec/edit. It doesn't have all the information necessary / some details are missing, but it's enough to implement the test table.

[hkatzdev]

Test Table is implemented at https://tables.area120.google.com/u/0/workspace/8JsRrAd7fEgd5jspaL4_qD/table/9gZ9xePJnfs2H65LCypkLZ.

[hkatzdev]

TODO: Figure out Feature label

[hkatzdev]

Without some sort of automation, implementing the exact form from production and keeping it updated seems unfeasible. Instead, the text is ignored, with only the form fields being accurate - that shouldn't change much, and if it does should be tested in the test table first. May explore automation but out of scope for entry test environment - perhaps an enhancement later?