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

Feature: customizeable TestCaseStatus #1932

Closed
atodorov opened this issue Sep 16, 2020 · 1 comment
Closed

Feature: customizeable TestCaseStatus #1932

atodorov opened this issue Sep 16, 2020 · 1 comment

Comments

@atodorov
Copy link
Member

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.

  • enable in admin
  • allow selection of color (in TP page) and status icons like TestExecutionStatus
  • get rid of the get_proposed(), get_confirmed(), is_confirmed() methods -> replace with a boolean field that indicates whether or not this TestCase is ready to be executed.
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.
@YouWhy
Copy link

YouWhy commented Sep 17, 2020

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
- 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
Projects
None yet
Development

No branches or pull requests

2 participants