0
Under review
While Unit test run why need to connect actual resources
We have identified that if we are not using actual values for DB and other resources for workflows it fails Unit tests.
It causes issue while unit test run when unit test container connects to actual DB and other resources, there might be chances of Data manipulation at Unit test level.
Служба підтримки клієнтів працює на UserEcho
Have you considered using mocks? The database will not be called if the database activity is replaced with a mock in the test. When the test is run the mocked activity will always output the provided data and never actually call the database.