we are trying to implement serenity to test mobile application using SeeTest automation tool. can anyone guide what will be best way. currently we are able to connect to the device with the help of wrappedSeeTestDriver.once the execution completes results are generated but screen shots are not captured. also operations like sendText("{ENTER}"); also not working. Any suggestions idea will be great help.
SeeTest (Mobile automation) support for serenity
431 Views Asked by azeem At
1
There are 1 best solutions below
Related Questions in SERENITY-BDD
- Eclipse color highlighting broken
- Wrong Theme being applied to PreferenceActivity with xml reference
- "Use Theme.AppCompat theme with this activity" Exception
- PrefererenceFragment Material Theme with Support Library
- Unable to use the Sphinx Readability theme
- Translucent theme with material
- How to retrieve data from wordpress database in php and display on a page?
- Different theme for each language in Eclipse
- How to properly create a child theme structure
- Drupal Zen theme without compass
Related Questions in SEETEST
- Eclipse color highlighting broken
- Wrong Theme being applied to PreferenceActivity with xml reference
- "Use Theme.AppCompat theme with this activity" Exception
- PrefererenceFragment Material Theme with Support Library
- Unable to use the Sphinx Readability theme
- Translucent theme with material
- How to retrieve data from wordpress database in php and display on a page?
- Different theme for each language in Eclipse
- How to properly create a child theme structure
- Drupal Zen theme without compass
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
To achieve BDD with SeeTest, you can use SpecFlow with C#. Below are high level Steps:
sendText("{ENTER}");: The sendText({Enter}) (or also the 'BKSP') is basically try to use the enter from the android keyboard, and it is a possibility that this application or specific activity on the application developed different.
If you are using seeTestAutomation and open the application in the reflection and spotify to the right place when you testing the enter, try to press manual in the the computer's keyboard 'enter', is it working?
Also please try with adb command (run command in seeTest) "adb shell input keyevent 66" (66 is the keycode for enter) and if this won't work - it means that the enter command is not implemented this view of the application.