Validating below quoted scenarios across test pyramids with E2E UI Tests, Integration Tests(including services and database layer validations) and Unit Tests.

Scenarios to be tested for Rider:

1. User should be able to login after successful registration with valid credentials
2. Forgot Password functionality should work as expected in case if user forgets credentials
3. Invalid credentials shouldn't let user login and prompt with an error message
4. User should be able to search for a driver with valid search string
5. Validate if location service is working as expected.
6. Clicking on floating action button to narrow/pin down to current location should work as expeceted.
7. Should be navigated to driver profile to view/contact driver info.
8. Clicking on call button should navigate to launch dialer keypad.

Scenarios to be tested for Driver: (Assuming app provides access to drive to accept rides/bookings/validate earnings etc)

1. Should be able to login as a driver with Valid Credentials.
2. Prompted with invalid credentials error message with wrong username/password.
3. Should be able to contact user after he/she books a cab.
4. Would be able to view current.

Scenario to be tested for Platinum Rider/Corporate Profile Rider: (Assuming premium service is avialble)

Would be validating all possible scenarios 1-8 mentioned for valid rider as above.
1. In addition to above scenarios benefits provieded to the user could be validated such as reduced prices, faster booking etc.