hackforla / hackforla/tables

Unit test set up - Research QUnit and GasT for unit test implementation

Open
#132 0 comments 0 reactions 0 assignees View on GitHub
Complexity: Large feature: Test Environment role: developer size: 3pt
Dominant language
JavaScript
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## Overview
As part of addressing technical debt for the Hack for LA Tables project, we need to implement unit testing to ensure the reliability of our onboarding/offboarding automation system (built with Google Apps Script). This issue tasks is to research QUnit and GasT for unit test implementation, documenting findings, and proposing a setup plan to improve code quality.

## Action Items
- [ ] **Research QUnit for Google Apps Script**:
- Investigate QUnit’s compatibility with GAS, focusing on testing scripts like `project_onboarding.gs`, `bot.gs`, and `ZoomAttendeeReport.gs`.
- Identify setup requirements (e.g., library integration, test runner configuration).
- Document advantages, limitations, and examples (e.g., testing `projectOnboardingAutomation`).
- [ ] **Research GasT for Google Apps Script**:
- Explore GasT’s features for GAS unit testing, including setup and integration with our CI/CD pipeline (GitHub Actions, `clasp`).
- Compare GasT with QUnit for ease of use, coverage, and community support.
- Provide sample test cases for key functions (e.g., `getRolePermission`, `setTrigger`).
- [ ] **Document findings** below

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.