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
Hello Team,
We are looking into re-using Components for our integration testing purposes. We plan on using a separate DI hierarchy for the testing purpose, and wanted to re-use most of our regular components with minor modifications. For example:
Here, we inherit the NetworkComponent and override urlSession, but the other members are inherited. Now we can use this TestNetworkComponent as part of the testing DI hierarchy.
Currently this approach does not work, since TestNetworkComponent is not picked up by needle's code generator and we run into runtime issues.
Is this something the team might be interested in adding support for? Or any recommendations to do things in a different way?
Thanks!
The text was updated successfully, but these errors were encountered:
Hello Team,
We are looking into re-using Components for our integration testing purposes. We plan on using a separate DI hierarchy for the testing purpose, and wanted to re-use most of our regular components with minor modifications. For example:
Now, when we want to create one for testing, we would like to have something like:
Here, we inherit the NetworkComponent and override urlSession, but the other members are inherited. Now we can use this TestNetworkComponent as part of the testing DI hierarchy.
Currently this approach does not work, since
TestNetworkComponent
is not picked up by needle's code generator and we run into runtime issues.Is this something the team might be interested in adding support for? Or any recommendations to do things in a different way?
Thanks!
The text was updated successfully, but these errors were encountered: