Jacob Maristany
Jacob Maristany
@TroyWalshProf , although, I realized I could solve this in the same way that you mentioned in #412
This is effectively what I'm doing now: ``` [SetUpFixture] public class TestLifeCycle { [OneTimeSetUp] public void AssemblyInitalize() { string deviceName = Config.GetValueForSection(ConfigSection.AppiumMaqs, "DeviceName"); if (deviceName == "iPad" || deviceName ==...
@TroyWalshProf Understood. I'm happy with the workaround I have and understand that it's incredibly specific. I've only left the issue open thus far in case you did want to pursue...
Ability to use relative paths for "app" capability in app.config under AppiumCapsMaqs w/ native apps
@TroyWalshProf Here's the NUnit version we have to run. ``` [SetUpFixture] public class TestLifeCycle { [OneTimeSetUp] public void AssemblyInitalize() { ... } ```
@rockfordlhotka We have two states to consider: what happens when the app comes to the foreground from the background and what we manually lock while in foreground due to "inactivity."...
@rockfordlhotka @TeresaLhotka , I realized today that sometimes we (users) put the app into the background temporarily as we check email/etc and then bring it back up in quick order....