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 test for translation cancel bulk action #2915

Open
MizukiTemma opened this issue Jul 18, 2024 · 1 comment · May be fixed by #3117
Open

Add test for translation cancel bulk action #2915

MizukiTemma opened this issue Jul 18, 2024 · 1 comment · May be fixed by #3117
Assignees
Labels
effort: low Should be doable in <4h good first issue Good for newcomers prio: low Not urgent, can be resolved in the distant future.

Comments

@MizukiTemma
Copy link
Member

Motivation

This is a follow-up issue for #2007 . Let's add some test for this new functionality 🧪

Proposed Solution

Add tests for the new bulk action which resets currently_in_translation status.

Alternatives

Leave it untested and live with higher threat of bugs 🐛

User Story

Additional Context

Design Requirements

@MizukiTemma MizukiTemma added good first issue Good for newcomers prio: low Not urgent, can be resolved in the distant future. blocked Blocked by external dependency effort: low Should be doable in <4h labels Jul 18, 2024
@MizukiTemma MizukiTemma added this to the 24Q3 milestone Jul 18, 2024
@JoeyStk JoeyStk changed the title Add test for trasnlation cancel bulk action Add test for translation cancel bulk action Jul 18, 2024
@MizukiTemma MizukiTemma removed the blocked Blocked by external dependency label Aug 21, 2024
@MizukiTemma
Copy link
Member Author

Not blocked anymore as #2007 is completed.

@theresantonie theresantonie self-assigned this Aug 30, 2024
@osmers osmers modified the milestones: 24Q3, 24Q4 Oct 2, 2024
@theresantonie theresantonie linked a pull request Oct 6, 2024 that will close this issue
@JoeyStk JoeyStk removed this from the 24Q4 milestone Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: low Should be doable in <4h good first issue Good for newcomers prio: low Not urgent, can be resolved in the distant future.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants