Hi, I normally contract in MSBI, SQL, Data Arcitecture, Oracle, .Net/.Net Core, API development, React, focusing on www.cryptostatto.com at the moment. Reach out if you see any synergy.
I am coming from it more that if we write applications which are data focused - integration tests are better. A great example could be coding in a portfolio swap for a known test case, if this is stubbed that stub can become stale quickly. In this example, I may store the stub as a json file (deserialised IList). This allows testers and analysts to put in their own test cases. I wrote about this here (kind of) dev.to/zakwillis/novel-tips-on-uni...
I think your point is valid, imagine if there is legacy code. Yes, I would probably setup up a separate unit test project as a means of understanding the code. However, where legacy systems exist, they are only understood by their outputs - which again leans towards integration testing, despite how slow the process may be compared to unit testing.
For further actions, you may consider blocking this person and/or reporting abuse
I am coming from it more that if we write applications which are data focused - integration tests are better. A great example could be coding in a portfolio swap for a known test case, if this is stubbed that stub can become stale quickly. In this example, I may store the stub as a json file (deserialised IList). This allows testers and analysts to put in their own test cases. I wrote about this here (kind of) dev.to/zakwillis/novel-tips-on-uni...
I think your point is valid, imagine if there is legacy code. Yes, I would probably setup up a separate unit test project as a means of understanding the code. However, where legacy systems exist, they are only understood by their outputs - which again leans towards integration testing, despite how slow the process may be compared to unit testing.