Test framework #69
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#69
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Once gitea/go-sdk#194 merged, I will send a similar PR to this project.
@lunny since the tests in go-sdk impruve a lot I dont think we nee souch extende tests:
if the go-sdk is tested the tea ony differs to it from user interactions
so the more tests go-sdk will get the less I think we need this
CI shoult take care of lint errors and if it can be compiled ...
Users will report the bugs a CI cant catch ...
what do you think?
@6543 I think currently you are right. Because tea is a simple wrap command tool of go-sdk. But I would like to hold this issue because in future, we may add more codes which maybe not tested in go-sdk.
I think we still need end-to-end tests, as we repeatedly struggled with commandline flags not being available / loosing their aliases / ...
Also newer features add some non-trivial git code, which would be nice to be tested.
The most basic test "framework" I can think of that would get us a long way, is calling the executable with different flag configurations and checking the exit code.
For git operations we could verify correct operation with actual
git
commands.