Tag integration tests which require public DNS #595
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#595
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?
@p4u1 mentioned that it's possible to run the test suite locally and only a few tests require public DNS. We should tag these tests so we can run only the local ones. This will help when we go for #584 and we split up the tests into e.g. "fast" / "slow" / "needs dns", etc.
@p4u1 you don't by any chance have a tip on how to find out which tests require public DNS do you? I thought a lot of them needed it... I was always running them with a public domain configured...