We want the Acquaintance class to represent someone we have paired with but is not our contact yet. We want to keep the information we paired with separate from our database.
Actual behavior
When we pair with a person, that person is immediately added into the database. This is not very wise because when we do so, when we return and try to add the person again, even though he is not in our chain yet, it will not add this block to the chain because it is already in the chain.
Steps to reproduce this behavior
Refactor according to UML.
Definition of Done
Class is made and test coverage >80%
The Acquaintance class should be implemented according to this image below
Member responsible: Luat
Duration: 1h
Priority: A
Claimed by: Naqib & Luat
Expected behavior
We want the Acquaintance class to represent someone we have paired with but is not our contact yet. We want to keep the information we paired with separate from our database.
Actual behavior
When we pair with a person, that person is immediately added into the database. This is not very wise because when we do so, when we return and try to add the person again, even though he is not in our chain yet, it will not add this block to the chain because it is already in the chain.
Steps to reproduce this behavior
Refactor according to UML.
Definition of Done
Class is made and test coverage >80% The Acquaintance class should be implemented according to this image below
Member responsible: Luat Duration: 1h Priority: A Claimed by: Naqib & Luat