Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No availability to press enter key after entering search text in the search bar of the app. #37

Closed
mfaisalkhatri opened this issue Mar 3, 2018 · 0 comments
Closed

No availability to press enter key after entering search text in the search bar of the app. #37

mfaisalkhatri opened this issue Mar 3, 2018 · 0 comments
Assignees
@WasiqB
Labels
severity: critical Issue is marked as critical. severity: high Issue is marked as high.
Milestone
Version 2.2.0

Comments

@mfaisalkhatri
Copy link
Collaborator

Description

Test Case: Verify by pressing the Enter Key after entering search text in the search bar of the Flipkart mobile app.
Test Steps: 01. Go to Flipkart App. 02. Tap on search bar, 03. Enter Text "Note 5" and press Enter key.
Expected Output - System should allow to enter text an press "Enter" key.
Actual Output - No method is provided to press "Enter" Key.
(Screenshot of the search window is attached for more details).

Environment

  • Appium server version: 1.7.2
  • Desktop OS version: Windows 8.1
  • coteafs-appium version:2.2.0 beta1
  • Mobile platform version: Android / 4.4.2
  • Real device / simulator:Real Device

scr-20180303-175854
@WasiqB WasiqB self-assigned this Mar 3, 2018
@WasiqB WasiqB added severity: critical Issue is marked as critical. severity: high Issue is marked as high. labels Mar 3, 2018
@WasiqB WasiqB added this to the Version 2.2.0 milestone Mar 3, 2018
WasiqB added a commit that referenced this issue Mar 9, 2018
@WasiqB
Fixed tickets #32, #35, #26, #36, #30, #28, #34, #33, #31, #29, #23, #24
1118107 
 and #37.
@WasiqB WasiqB closed this as completed Mar 9, 2018
WasiqB added a commit that referenced this issue Oct 2, 2018
@WasiqB
Fixed tickets #32, #35, #26, #36, #30, #28, #34, #33, #31, #29, #23, #24
50a37d8 
 and #37.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@WasiqB WasiqB

Labels
severity: critical Issue is marked as critical. severity: high Issue is marked as high.
Projects
None yet
Milestone
Version 2.2.0
Development

No branches or pull requests
2 participants
@WasiqB @mfaisalkhatri