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

Add tests of PRs same as for other eventyay components #84

Open
mariobehling opened this issue May 13, 2024 · 1 comment
Open

Add tests of PRs same as for other eventyay components #84

mariobehling opened this issue May 13, 2024 · 1 comment
Labels

Comments

@mariobehling
Copy link
Member

Eventyay-Talk has a number of tests. Please also add more tests to this repository.

Compare:
Screenshot from 2024-05-13 23-24-30

@untari
Copy link
Contributor

untari commented May 16, 2024

Current list of tests we should have on eventyay-tickets (please correct where needed):

  • build: currently missing
  • docker: allows running manually and runs on every push to the main or development branch and when a tag is added
  • docs runs when push and PRs targeting master but only if changes are made outside the specified paths to ignore related to the src/pretix/locale/, src/pretix/static/, and src/tests/ directories
  • strings runs when push and PRs targeting master branch, specifically when changes are made within the doc/ and src/pretix/locale/ directories
  • style runs when push and PRs targeting master branch, but only if changes are made outside src/pretalx/locale/, src/pretalx/static/
  • tests runs when push and PRs targeting test but only if changes are made outside the specified paths to ignore related to doc/**', 'src/pretalx/locale/**' directories

TODO:

  • build add build test in the eventyay-tickets repo and run in master branch
  • build make it run in development branch
  • docker make it run in development branch
  • docs make it run in development branch
  • strings make it run in development branch
  • style make it run in development branch
  • tests make it run in development branch

This comment has been edited on the name of branches. It should be run in master and development branches instead of main

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants