dibley1973 / dibware.salon Goto Github PK

Leave this issue open and use it to assign miscellaneous test coverage improvements to.

Provide a decent level of unit test cover to existing Shared Kernel objects and structures

It is acceptable when...

• An Add(PositiveInteger) method is implemented
• An Subtract(PositiveInteger) method is implemented
• An ++(PositiveInteger) method is implemented
• An --(PositiveInteger) method is implemented
• All new members are covered by unit tests

It is acceptable when...

• The concept is developed within it's own feature branch
• The concept will be represented by an object
• The object derives from a Entity
• The object has an Duration property
• The object has a Technician property
• The object has a Cost property of type Money
• The object can contain multiple "sub" single or other MultipleTreatment objects
  -- A discount of cost can be applied to the total of the sub treatments
  -- A discount of time can be applied to the total of the sub treatments
• The object has a static factory Create() method
• The Create() method, and properties are covered with units tests with at least 90% code coverage

Related to #6, which must be completed first.

It is acceptable when...

• Add() and Subtract() members are implemented
• += and -= members re implemented
• Rollover results of minutes calculations which exceed 59 into hours and minutes
• Negative results are not permitted, such operations should result in zero
• New members are covered by unit tests with at least 90% coverage

It is acceptable when...

The concept is developed within it's own feature branch
The concept will be represented by an object
The object derives from a Entity
The object has an Duration property of type Duration
The object has a Technician property
The object has a Cost property of type Money
The object has a static factory Create() method
The Create() method, and properties are covered with units tests with at least 90% code coverage

It is acceptable when...

• The concept is developed within it's own feature branch
• The concept will be represented by an object
• The object derives from a ValueObject
• The object has an Hours property
• The object has a Minutes property
• The object has a static factory Create() method
• The Create() method, and properties are covered with units tests with at least 90% code coverage

Related to #6 .

It is acceptable when...

• IEquality<Duration> members are implemented
• Equals members are implemented
• == and != members re implemented
• New members are covered by unit tests with at least 90% coverage

It is acceptable when...

• It derives from ValueObject
• It has a currency symbol property
• It has a super unit portion property
• It has a sub-unit portion property
• It has a number of sub-units in one super unit property
• The object is covered by at least 95% code coverage with all major logic flows covered

Ref:
https://en.wikipedia.org/wiki/Denomination_(currency)