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
I am currently facing a challenge with my Flutter application's testing process. Initially, I developed a comprehensive test suite using Fluttium for the native app. However, our registration and signup flow has now been transitioned from the native app to a web-based platform. Given the substantial investment of time and effort in creating the existing test suite with Fluttium, I am seeking guidance on how to automate the testing of the web view without migrating away from Fluttium.
Considering my situation, I am keen to explore solutions that would allow me to seamlessly integrate web view testing within the Fluttium framework, ensuring that the work already undertaken is leveraged effectively. I am open to any recommendations or strategies that would enable me to adapt the existing test suite to accommodate the web view changes, without necessitating a switch to alternative testing frameworks such as Patrol or Honey.
Your insights, suggestions and expertise in this matter would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Description
I am currently facing a challenge with my Flutter application's testing process. Initially, I developed a comprehensive test suite using Fluttium for the native app. However, our registration and signup flow has now been transitioned from the native app to a web-based platform. Given the substantial investment of time and effort in creating the existing test suite with Fluttium, I am seeking guidance on how to automate the testing of the web view without migrating away from Fluttium.
Considering my situation, I am keen to explore solutions that would allow me to seamlessly integrate web view testing within the Fluttium framework, ensuring that the work already undertaken is leveraged effectively. I am open to any recommendations or strategies that would enable me to adapt the existing test suite to accommodate the web view changes, without necessitating a switch to alternative testing frameworks such as Patrol or Honey.
Your insights, suggestions and expertise in this matter would be greatly appreciated.
The text was updated successfully, but these errors were encountered: