How would you integration test a monolithic application?

Discussions
,
1

Hello there!

Consider a monolithic application where:

  • Actions can generally only be performed via the UI.
  • The UI can’t be decoupled from backend functionality.
  • The majority of backend functionality can’t be triggered via API.
  • The application relies on scheduled jobs to process data.
  • The application stores everything in a single database.

If you were tasked with finding a way to set up integration tests for such a system, how would you approach it?

2

Hmm the application is a monolith, when you say Integration, do you mean integration between the parts of the application?

3

Yep that’s what I was thinking with it. I probably should have made it clearer, maybe the question is too vague :sweat_smile:

4

If it is possible to monitor the components’ states (API sniffer, internal monitors, access to the DB, logs, and more), you could approach it like E2E testing, where you verify the complete flow of actions.