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

Chore: Implement automated tests & test CI pipeline #43

Open
Adammatthiesen opened this issue May 2, 2024 · 1 comment · May be fixed by #46
Open

Chore: Implement automated tests & test CI pipeline #43

Adammatthiesen opened this issue May 2, 2024 · 1 comment · May be fixed by #46
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@Adammatthiesen
Copy link
Member

Is your chore related to a problem? Please describe.
We currently have no way to test functionality or new features within the project.

Describe the solution you'd like
We need to implement and start utilizing a CI/CD Pipeline

Additional context
Testing is important as it will not only help streamline our process but will be required for 1, the dependency management, as well as to ensure we do not release a version that does not work once we start releasing packages!

@Adammatthiesen Adammatthiesen added enhancement New feature or request help wanted Extra attention is needed labels May 2, 2024
@jdtjenkins jdtjenkins changed the title Chore: Implement CI/CD Testing Pipeline Chore: Implement automated tests & test CI pipeline May 2, 2024
@jdtjenkins jdtjenkins self-assigned this May 2, 2024
Copy link
Contributor

Branch issue-0043 created for issue: Chore: Implement automated tests & test CI pipeline

create-issue-branch bot added a commit that referenced this issue May 3, 2024
@Adammatthiesen Adammatthiesen mentioned this issue Jun 16, 2024
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants