fjborquez / aang

0 stars 0 forks source link

Update House #25

Closed Norbbs closed 5 months ago

Norbbs commented 6 months ago

As a Data Owner I want to update a house data to the other users So that they can access to completely updated data and utilize the data related to the house for their respective needs

Definition Of Ready (DoR)

Definition Observations
  • - [x]
The story meet the INVEST and SMART criteria
  • - [x]
Dependencies identified and resolved
  • - [x]
Written acceptance criteria with test scenarios, understood by the team and agreed upon
  • - [x]
The user story was understood and agreed upon in a refinement session with the dev team
  • - [x]
The team has an idea of how to make the demonstration of the finished story

Scope

  1. Update data in the entity Person:
    • id (integer, mandatory).
    • description (string, mandatory, max 30 chatacters).
    • city_id (foreign key)

Out of scope

  1. create, delete and other non-update processes.
  2. For the cities entity: province, region and country are out of scope.

Acceptance Criteria

AC GIVEN WHEN THEN
  • - [ ]
1 Update house successfully a house description correctly the house update process is triggered the house will be updated to the table houses.
  • - [ ]
2 Update house successfully with isDefault property is true a house description correctly and isDefault property is false the house update process is triggered AND the person has NOT any house registered the house will be updated to the table houses with isDefault property true.
  • - [ ]
3 Update house successfully with isDefault property is true a house description correctly and isDefault property is true the house update process is triggered AND the person has at least one house registered the house will be updated to the table houses with isDefault property true AND the old one set the isDefault property false and will be updated with isDefault property false.
  • - [ ]
4 Update house successfully with isDefault property is false a house description correctly and isDefault property is false the house update process is triggered AND the person has at least one house registered the house will be updated to the table houses with isDefault property false.
  • - [ ]
5 No update new house because of lack of description a house description null or empty the house update process is triggered the house WON'T be updated to the table houses.
  • - [ ]
6 No update the house because of maximum characters allows a house description with more than 30 characters the house update process is triggered a new house WON'T be updated to the table houses.
  • - [ ]
7 No update house because of data duplication a house description correctly AND person has one house with the SAME description in the SAME city registered the house update process is triggered a new house WON'T be added to the table houses .
  • - [ ]
8 No update house because of lack of city a house's city is null or empty the house update process is triggered the house WON'T be updated to the table houses.
  • - [ ]
9 Update house NOT because of data duplication a house description correctly AND person has one house with the SAME description but NOT in the SAME city registered the house update process is triggered the house will be updated to the houses table.
  • - [ ]
10 Update house NOT because of data duplication a house description correctly AND person has one house with a DIFFERENT description but in the SAME city registered the house update process is triggered the house will be updated to the table houses.
  • - [ ]
11 Update house NOT because of data duplication a house description correctly AND person has one house with a DIFFERENT description in a DIFFERENT city registered the house update process is triggered the house will be updated to the table houses.
  • - [ ]
12 No update house successfully with isDefault property is false a house description correctly AND this user has ALL registered houses with by default property in FALSE the house update process is triggered the house WON'T be updated to the table houses.

Definition of Done (DoD)

Definition Result
  • - [ ]
All acceptance criteria have been met
  • - [ ]
No significant or critical defects
  • - [ ]
Deskcheck ceremony has been made
  • - [ ]
Keep minimum test coverage of 80% over the necessary code and components
  • - [ ]
Technical documentation published
  • - [ ]
Spike, PoC or benchmarks findings documented