-
Notifications
You must be signed in to change notification settings - Fork 3
Open
2 / 42 of 4 issues completedLabels
ciRelated to the CI systemRelated to the CI systemenhancementNew feature or requestNew feature or requestrefactorRelated to refactors of the codebaseRelated to refactors of the codebase
Description
Problem
Deployment and testing is currently a chore right now with cloning the ARS and editing it to a test setup with a generic username and having bash scripts to send JSONs to the websocket to see its response in the bot.
Test coverage is pretty bad right now too.
Solution
- Host ARS in some way (Docker image on DockerHub?) and run that in actions on every Pull Request. Make sure that the code in ARS does not get leaked. Tracked in CI: Create Github Action Specs for running and hosting ARS #12
- Make Integration tests to interact with this container. Tracked in Tests: Improve Code Coverage #11
- Unit testing might be irrelevant but still give it a thought and refactor in such a way that we can test it in units. Tracked in Tests: Improve Code Coverage #11
- Add lint checks and format checks on merges and PRs. Tracked in CI: Add lint checks and format checks on PRs #25
Sub-issues
Metadata
Metadata
Assignees
Labels
ciRelated to the CI systemRelated to the CI systemenhancementNew feature or requestNew feature or requestrefactorRelated to refactors of the codebaseRelated to refactors of the codebase