↧
Answer by user3198764 for Are (database) integration tests bad?
In the .Net world I have a habit of creating a testing project and creating tests as a method of coding / debugging / testing round trip minus the UI. This is an efficient way for me to develop. I...
View ArticleAnswer by Thomas Junk for Are (database) integration tests bad?
Unit Tests and Integration Tests are orthgonal to each other. They offer a different view on the application you are building. Usually you want both. But the point in time differs, when you want which...
View ArticleAnswer by S.D. for Are (database) integration tests bad?
You are right to think of such a unit test as incomplete. The incompleteness is in the database interface being mocked. Such naive mock's expectation or assertions are incomplete. To make it complete,...
View ArticleAnswer by Bruno for Are (database) integration tests bad?
The author of the blog article you refer to is mainly concerned with the potential complexity that can arise from integrated tests (although it is written in a very opinionated and categorical way)....
View Article
Image may be NSFW.
Clik here to view.
Clik here to view.
Answer by Nick Alexeev for Are (database) integration tests bad?
Unit tests don't catch all defects. But they are cheaper to set up and (re)run compared that other kinds of tests. The unit tests are justified by combination of moderate value and low-to-moderate...
View ArticleAnswer by el.pescado - нетвойне for Are (database) integration tests bad?
Database integration tests are not bad. Even more, they are necessary.You probably have your application split into layers, and it's a good thing. You can test each layer in isolation by mocking...
View ArticleAnswer by Jon Raynor for Are (database) integration tests bad?
No, they are not bad. Hopefully, one should have unit and integration tests. They are used and run at different stages in the development cycle.Unit TestsUnit tests should be run on the build server...
View ArticleAnswer by Jeff Bowman for Are (database) integration tests bad?
Write the smallest useful test you can. For this particular case, an in-memory database might help with that.It is generally true that everything that can be unit-tested should be unit-tested, and...
View ArticleAnswer by vidalsasoon for Are (database) integration tests bad?
External dependencies should be mocked because you can't control them (they might pass during the integration testing phase but fail in production). Drives can fail, database connections could fail for...
View ArticleAnswer by Froome for Are (database) integration tests bad?
You need both.In your example if you were testing that a database in a certain condition, when the findByKeyword method is run you get the data back you expect this is a fine integration test.In any...
View ArticleAnswer by D Stanley for Are (database) integration tests bad?
One of my co-workers maintains that integration tests are all kinds of bad and wrong - everything must be unit-tested,That's a little like saying that antibiotics are bad - everything should be cured...
View ArticleAre (database) integration tests bad?
Some people maintain that integration tests are all kinds of bad and wrong - everything must be unit-tested, which means you have to mock dependencies; an option which, for various reasons, I'm not...
View Article
More Pages to Explore .....