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
Our multi-module project was previously using a per-module configuration for fladle. This was useful, and we did this before full-adle was created. It's a bit messy and also requires developers to remember to configure each module with fladle.
One benefit of this approach however, was the ability to use to full suite of configuration options on a per-module basis. This includes the ability to decide with devices should be used for tests. This provides the ability to do things like run on physical devices for certain modules, but use emulators for others. Is there a way to do this with fulladle?
Note: It would also be very useful to be able to configure if test-orchestrator should be used with the fulladleModuleConfig block.
The text was updated successfully, but these errors were encountered:
Our multi-module project was previously using a per-module configuration for fladle. This was useful, and we did this before full-adle was created. It's a bit messy and also requires developers to remember to configure each module with fladle.
One benefit of this approach however, was the ability to use to full suite of configuration options on a per-module basis. This includes the ability to decide with devices should be used for tests. This provides the ability to do things like run on physical devices for certain modules, but use emulators for others. Is there a way to do this with fulladle?
Note: It would also be very useful to be able to configure if test-orchestrator should be used with the fulladleModuleConfig block.
The text was updated successfully, but these errors were encountered: