Worse yet, developers who have not used any mocking frameworks before get completely confused about the term mock and what it means. Now the programmers cannot tell what they are dealing with. There is nothing wrong with this except that when someone else comes along and needs to use an actual mocking framework such as EasyMock or Mockito. But calls them "mocks", even using the word "mock" in the class names. In this case, should another program which is an wrapper program be introduced to the users, they will become confused because they will see two programs described the same way, but with different functionality.Īn example - A "classic" of this I've seen over and over again in development teams is where someone starts writing stub or fake classes for testing purposes. Terminology is not that important unless it is used incorrectly and creates confusion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |