ict.ken.be
Mock framework vs manual mocking
Categories
.Net
(22)
Android
(1)
Angularjs
(2)
Azure
(5)
BitCoin
(1)
CSS
(4)
Docker
(2)
EF
(6)
Gatsbyjs
(1)
Git
(5)
GraphQL
(2)
HTML
(5)
IIS
(12)
Javascript
(17)
Kubernetes
(2)
Linq
(1)
Linux
(5)
Mercurial
(6)
Messagent
(17)
Mobile
(4)
mojoPortal
(2)
Network
(14)
Nodejs
(7)
Notes
(23)
Patterns
(8)
Reactjs
(3)
Red5
(1)
RegEx
(1)
Security
(12)
Shortcuts
(5)
SQL Server
(23)
Testing
(10)
Visual Code / VSCode
(1)
Visual Studio
(16)
WebApi
(7)
Windows
(19)
Related Posts
Selenium Unable to cast object of type 'System.String' to type 'System.Collections.Generic.Dictionary
xunit nuget - A numeric comparison was attempted on - Error
Wallaby
The Joel Test
Viewresult into html, best error ever.
Categories:
Testing
Previous Post <<
>> Next Post
PRO
Fake implementations of abstractions.
Complete control over mock object functionality.
No need to learn frameworks.
CON
Each mock object adds more code.
As complexity grows, so do mock objects.
What if interface changes or interaction logic changes?
Total time needed to write all the mocks.
Previous Post <<
>> Next Post
New Comment