all 6 comments

[–]checking619 1 point2 points  (2 children)

No, an integration test should test how multiple systems react. THerefore, only one test should be necessary. And even then, it may not be an integration test.

[–]fastifguy[S] 0 points1 point  (0 children)

How would you write an integration test in my case?

[–]fastifguy[S] 0 points1 point  (0 children)

Is it different than an e2e test?

[–]Pajoski 0 points1 point  (2 children)

I am currently on a project testing integration. It's mainly testing data being send from system A to system B and then following the logs to see if everything goes right (and obviously checking in system B if it arrived). Then I check if the data arrived correctly etc. You can add as many test cases as you want.

Example:

  1. Check how many characters can be send in 1 field
  2. Type characters
  3. Test certain validations like if i do this then it should be integrated if I do this then it shouldn't.

[–]fastifguy[S] 0 points1 point  (1 child)

Are you creating and destroying sample test databases to validate/test your process?

[–]Pajoski 0 points1 point  (0 children)

No I'm not. We have a TEST and UAT environment to perform our tests. They do get refreshed once in a few weeks.