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
I have been trying to understand how different developers approach integration testing, especially when working with applications that have multiple layers such as APIs, services, and databases. On paper the idea is clear, but in real projects it becomes less obvious where integration testing adds the most value.
Do you focus mainly on critical paths or do you test a wide range of interactions between components. How do you decide when an interaction is important enough to test as a group rather than as isolated units. I often find myself unsure whether I am testing too much or not enough, and I am interested in hearing how others find the right balance.
If you have patterns, habits, or simple rules that guide your decisions, I would appreciate learning from your experience. Understanding how different teams structure their integration tests would help me refine my own approach.
GeneralGeneral topics and discussions that don't fit into other categories, but are related to GitHub
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have been trying to understand how different developers approach integration testing, especially when working with applications that have multiple layers such as APIs, services, and databases. On paper the idea is clear, but in real projects it becomes less obvious where integration testing adds the most value.
Do you focus mainly on critical paths or do you test a wide range of interactions between components. How do you decide when an interaction is important enough to test as a group rather than as isolated units. I often find myself unsure whether I am testing too much or not enough, and I am interested in hearing how others find the right balance.
If you have patterns, habits, or simple rules that guide your decisions, I would appreciate learning from your experience. Understanding how different teams structure their integration tests would help me refine my own approach.
BetaWas this translation helpful?Give feedback.
All reactions