dancodingbr / riskmanager Goto Github PK

Feature: Choose the effective action plans for the problem

This issue is focused on the implementation of the related feature proposed in the requirements doc.

More info here:
https://github.com/dancodingbr/riskmanager/blob/main/docs/02_requirements.md#feature-choose-the-effective-action-plans-for-the-problem
https://github.com/dancodingbr/riskmanager/blob/main/docs/02_ux-ui-design/02_ux-ui-wireframes.pdf

Bug: Duplicating analyzed result after save it

Version: v1.0.0 (demo release)

System Operator: any

What would you want to do? Edit and save an analyzed result.

Steps to reproduce:

1. In analyzing results form, select a problem.
2. After list the respective analyzed results, choose one to Edit.
3. On edit analyzed result form, click on save button.

Expected results:

1. List the same quantity of analyzed result showed before edited one.

Actual results:

1. The analyzing results form is showing a duplicated analyzed result that I was just changed on edit form.

This issue is focused on discussing the needs of retire or replace some test tools used in the development process, exceptionally, Pactum, CucumberJS (frontend tier) and Cucumber (backend tier).

Initially, the idea behind to use this test tools as a manner to align the business goals proposed in the features and the product development. Starting from the common step definitions here, and specialising them in both frontend (here) and backend (here) tiers.

But, I'm not satisfied with the result that I expected in terms of test automation readability. I think the result that I obtained is so confusing to maintain in the next iterations. See these source code examples obtained here, here and draw your own conclusions.

So, I would like to listen your opinions about the needs of continuing using these tools for this project. If this a case of overengineering, and just the another test tools currently used to this project is enough. Or it's possible to improve these tests and it's a good ideia to maintain them.

In PDCA cycle, it's common that the action plans chosen as effective are considered a good solutions, thus enabling the promotion of continuous improvement.

These effective action plans could be used to solve new problems that it would be registered by the user in the next PDCA cycle iterations, or in other words, retrofit the PDCA cycle with effective action plans.

So, this issue is focused on discussing the retrofit action plans in the next iterations of PDCA cycle.

For example: Imagine that "Study 8 hours per week on next semester" action plan is elected as effective. So, If I'll register new problem called "Bad grades on SAT test", the user could use that effective action plan instead of analyze it once again.

Feature: Register a problem

This issue is focused on the implementation of the related feature proposed in the requirements doc.

More info here:
https://github.com/dancodingbr/riskmanager/blob/main/docs/02_requirements.md#feature-register-a-problem
https://github.com/dancodingbr/riskmanager/blob/main/docs/02_ux-ui-design/02_ux-ui-wireframes.pdf

This issue is focused on writing more tests in both frontend and backend tiers to expand the test coverage.

Feature: Create potential action plans to solve a problem

This issue is focused on the implementation of the related feature proposed in the requirements doc.

More info here:
https://github.com/dancodingbr/riskmanager/blob/main/docs/02_requirements.md#feature-create-potential-action-plans-to-solve-a-problem
https://github.com/dancodingbr/riskmanager/blob/main/docs/02_ux-ui-design/02_ux-ui-wireframes.pdf

Feature: Register tasks to do for each action plan

This issue is focused on the implementation of the related feature proposed in the requirements doc.

More info here:
https://github.com/dancodingbr/riskmanager/blob/main/docs/02_requirements.md#feature-register-tasks-to-do-for-each-action-plan
https://github.com/dancodingbr/riskmanager/blob/main/docs/02_ux-ui-design/02_ux-ui-wireframes.pdf

This issue is focused on discussing improvements and receive new ideas that could be applied to the UI/UX project.