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

Extend app template with test project #120

Open
2 tasks
Tracked by #90
RonnyB71 opened this issue Jul 8, 2022 · 1 comment
Open
2 tasks
Tracked by #90

Extend app template with test project #120

RonnyB71 opened this issue Jul 8, 2022 · 1 comment
Labels
kind/chore Technical tasks/debt needed in order to maintain a healthy system or otherwise improve dev processes quality/engineering

Comments

@RonnyB71
Copy link
Member

RonnyB71 commented Jul 8, 2022

Goal: Run tests as part of apps pipeline and encourage best practices.

Update 01.09.2022

Moving this out of the epic as it's not critical for the V7 release.

Tasks

  • Run tests as part of build
  • Warn the application developer on deploy if tests are red
@RonnyB71 RonnyB71 changed the title Extend app template with test projectGoal: Run tests as part of apps pipeline and encourage best practices. Extend app template with test project Jul 8, 2022
@RonnyB71 RonnyB71 added solution/apps kind/chore Technical tasks/debt needed in order to maintain a healthy system or otherwise improve dev processes quality/engineering labels Jul 8, 2022
@olemartinorg
Copy link
Contributor

olemartinorg commented Feb 1, 2023

Gitea is working on a github actions-like feature: https://blog.gitea.io/2022/12/feature-preview-gitea-actions/

Right now, Studio seems to be hacking together their own log of releases (mapping to the specific commit on master that was 'tagged' to release), but they're not propagating this back to git(ea) in a way where these tags are stored in the repo. We could leverage the releases functionality in gitea to tag commits, run release workflows to deploy, etc. The functionality should be somewhat compatible with github, and if it's a release workflow that pushes an app to an environment (instead of Studio doing this directly) we could help separate such actions and make them independent of Studio.

This could also make it possible for app developers to write their own tests, and run these on PR, release, etc. And it could make it possible for us to extend the template at some point, with a suggested action to run automatically generated tests (#122).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/chore Technical tasks/debt needed in order to maintain a healthy system or otherwise improve dev processes quality/engineering
Projects
Status: No status
Development

No branches or pull requests

2 participants