-
-
Notifications
You must be signed in to change notification settings - Fork 299
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
Feature: customizeable TestCaseStatus #1932
Labels
Comments
atodorov
added a commit
that referenced
this issue
Sep 16, 2020
a request has come that we keep this model and instead of making the field binary allow more customizations. Will play nicely with the redesigned TestPlan page.
I thought you are getting rid of the Boolean field for Test Case Status and keeping Proposed, Confirmed, Archived, Needs Update. I think it makes sense to keep it the way it is. |
atodorov
added a commit
that referenced
this issue
Nov 4, 2020
NOTE: the previous implementation seems to work fine for views and with API calls when executed live. However it causes one test to fail b/c it can't find the 'CONFIRMED' status! This implementation is not the best one but is functionally equivalent and seems to work. Also all of this will be refactored as part of #1932 very soon.
atodorov
added a commit
that referenced
this issue
Nov 4, 2020
NOTE: the previous implementation seems to work fine for views and with API calls when executed live. However it causes one test to fail b/c it can't find the 'CONFIRMED' status! This implementation is not the best one but is functionally equivalent and seems to work. Also all of this will be refactored as part of #1932 very soon.
atodorov
added a commit
that referenced
this issue
Nov 5, 2020
NOTE: the previous implementation seems to work fine for views and with API calls when executed live. However it causes one test to fail b/c it can't find the 'CONFIRMED' status! This implementation is not the best one but is functionally equivalent and seems to work. Also all of this will be refactored as part of #1932 very soon.
atodorov
added a commit
that referenced
this issue
Nov 5, 2020
NOTE: the previous implementation seems to work fine for views and with API calls when executed live. However it causes one test to fail b/c it can't find the 'CONFIRMED' status! This implementation is not the best one but is functionally equivalent and seems to work. Also all of this will be refactored as part of #1932 very soon.
atodorov
added a commit
that referenced
this issue
Nov 20, 2020
atodorov
added a commit
that referenced
this issue
Nov 20, 2020
- new DB migrations - update docs - add admin page to edit these statuses - Remove get_confirmed(), get_proposed() methods and update tests to match - Because there could be more than 1 confirmed statuses update API, views and JavaScript to take that into account
atodorov
added a commit
that referenced
this issue
Nov 20, 2020
- new DB migrations - update docs - add admin page to edit these statuses - Remove get_confirmed(), get_proposed() methods and update tests to match - Because there could be more than 1 confirmed statuses update API, views and JavaScript to take that into account
atodorov
added a commit
that referenced
this issue
Dec 1, 2020
- new DB migrations - update docs - add admin page to edit these statuses - Remove get_confirmed(), get_proposed() methods and update tests to match - Because there could be more than 1 confirmed statuses update API, views and JavaScript to take that into account
asankov
pushed a commit
to asankov/Kiwi
that referenced
this issue
Dec 2, 2020
NOTE: the previous implementation seems to work fine for views and with API calls when executed live. However it causes one test to fail b/c it can't find the 'CONFIRMED' status! This implementation is not the best one but is functionally equivalent and seems to work. Also all of this will be refactored as part of kiwitcms#1932 very soon.
asankov
pushed a commit
to asankov/Kiwi
that referenced
this issue
Dec 2, 2020
- new DB migrations - update docs - add admin page to edit these statuses - Remove get_confirmed(), get_proposed() methods and update tests to match - Because there could be more than 1 confirmed statuses update API, views and JavaScript to take that into account
asankov
pushed a commit
to asankov/Kiwi
that referenced
this issue
Dec 2, 2020
NOTE: the previous implementation seems to work fine for views and with API calls when executed live. However it causes one test to fail b/c it can't find the 'CONFIRMED' status! This implementation is not the best one but is functionally equivalent and seems to work. Also all of this will be refactored as part of kiwitcms#1932 very soon.
asankov
pushed a commit
to asankov/Kiwi
that referenced
this issue
Dec 2, 2020
- new DB migrations - update docs - add admin page to edit these statuses - Remove get_confirmed(), get_proposed() methods and update tests to match - Because there could be more than 1 confirmed statuses update API, views and JavaScript to take that into account
asankov
pushed a commit
to asankov/Kiwi
that referenced
this issue
Dec 2, 2020
- new DB migrations - update docs - add admin page to edit these statuses - Remove get_confirmed(), get_proposed() methods and update tests to match - Because there could be more than 1 confirmed statuses update API, views and JavaScript to take that into account
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar to TestExecutionStatus the TestCaseStatus should become customizeable. ATM we support translations of the names only. This feature will allow more semantics behind TestCases and more flexibility into organizing the workflow.
The text was updated successfully, but these errors were encountered: