You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our specs are not the most pretty ones out there. They need some refactoring.
One goal with this gem is to make it as easy as possible to add new resources. Repositories, Models and Mappers does not include any logic at all. These classes does not need any testing. If we instead focus on testing Repository::Base, Model::Base and Mapper::Base then all we need to test for each new resource is the integration with Fortnox, that it really works. We should therefore:
We should put this on hold for a bit. #149 will change the spec landscape quite a bit and it might be better if we did the refactoring of the test suite after the split.
Our specs are not the most pretty ones out there. They need some refactoring.
One goal with this gem is to make it as easy as possible to add new resources.
Repositories
,Models
andMappers
does not include any logic at all. These classes does not need any testing. If we instead focus on testingRepository::Base
,Model::Base
andMapper::Base
then all we need to test for each new resource is the integration with Fortnox, that it really works. We should therefore:For the new base gem, see #149:
Model::Base
(and all helper classes)Mapper::Base
(and all helper classes)Repository::Base
(and all helper classes)For this gem:
The text was updated successfully, but these errors were encountered: