You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
4So you're focussing on the relevance of a single chapter heading, and ignoring the fact his entire book is titled "Unit Testing Principles, Practices, and Patterns". That's besides how he's conflated the concepts of unit tests and integration tests in his article too. It's very charitable indeed to suggest we should read more of this author rather than less! 😂Steve– Steve2024-09-25 07:36:35 +00:00Commented Sep 25, 2024 at 7:36
-
1@Steve integration testing is a form of unit testing, technically. It uses the same technical tools, but tests application components in combination rather than separately.jwenting– jwenting2024-09-25 09:53:14 +00:00Commented Sep 25, 2024 at 9:53
-
2@jwenting, it's certainly a form of testing, but "unit testing" surely relates to the testing of "units", not the testing of any kind of assemblage or system of them. At least that's my understanding.Steve– Steve2024-09-25 10:38:45 +00:00Commented Sep 25, 2024 at 10:38
-
8@Steve There is no universal agreed definition of where unit tests ends and integration tests begin. I don't know what definition Khorikov uses, but it is perfectly reasonable to argue that a test which involves a database is a unit test if that database can be considered an implementation detail inside the unit under test and the test runs in isolation from other tests. In any case, the terminology is not the important issue, the question is if mocking the database in automated tests results in more or less robust code.JacquesB– JacquesB2024-09-25 17:51:24 +00:00Commented Sep 25, 2024 at 17:51
-
1@Steve: I am not focussing on the relevance of a "single chapter heading". I recommend you have a look into the book, too, before judging. And yes, though the book is titled "Unit Testing ...", it also contains a clearly separated section about integration testing, That does not make the book worse,Doc Brown– Doc Brown2024-09-27 06:09:40 +00:00Commented Sep 27, 2024 at 6:09
|
Show 6 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you