Automation for abra test suite? #401
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#401
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We failed to catch #396 because we don't have automated integration testing. Some great work was done in https://git.coopcloud.tech/coop-cloud/abra/src/branch/main/tests but it's easy to forget to run this and you need to set up a test environment each time. I think it might make sense to try to consider setting up some automation here. Maybe something like:
*.ci-test.coopcloud.tech
)Unsure how easy / hard this would be to get working well & reliably.
A small start would be good, perhaps. Very open to suggestions & advise here.
Automation for test suite?to Automation for abra test suite?Another run at a bash-based setup: coop-cloud/abra#338
More plans: https://pad.autonomic.zone/kdLrPXMSSb2TZezCBhdYtw?view
Resolution is in: https://docs.coopcloud.tech/federation/resolutions/in-progress/012/
I'm working on this!
p4u1 referenced this issue2024-03-11 12:57:14 +00:00