Skip to content

Instantly share code, notes, and snippets.

@enriquesanchezb
Last active October 27, 2019 18:24
Show Gist options
  • Save enriquesanchezb/4e0d3cb424f9903378e37ee3cce9b752 to your computer and use it in GitHub Desktop.
Save enriquesanchezb/4e0d3cb424f9903378e37ee3cce9b752 to your computer and use it in GitHub Desktop.
QE Challenge 2019

At Cabify we are always testing new features that add value to our users. Could you help us to test our new functionality: Price Calculator?

What is Price Calculator?

We want to help users to choose what kind of journey they want to do and how much this journey will cost. To do it, we want to provide users a new tool to calculate the price of a journey from the most common start points to the most common destination points and get the estimated price for the journey. Once you have the estimation, you can order a car or you can calculate a new journey.

The price for each user is unique and it depends from different things (#journeys for the user, mean journey time for this user, etc.). To do it, we show to the user a 3-number token that the user has to memorise and include in the estimation. The price for a journey depends on distance and vehicle type (Lite: standard price, Executive: 10% expensive about Lite price).

You can find this feature in this APK for Android apps and you can use it with this credentials: user@qabify.com/1234Abc.

What do you have to do?

  1. You have to create a Test Plan with all the test cases you think are necessary to test all the functionality. Please, be exhaustive and clear with your tests cases, imagine this test plan will be executed by the rest of the team.

  2. We know this feature has bugs, report all the bugs you find in the app in the same way you will do if you work at Cabify.

  3. Automate it! It will be amazing if you are able to show us your abilities as Test Engineer and you automate the tests cases you write. We value the code quality, the number of test cases, if you use design patterns...

NOTE: Tests cases, bugs, documentation... HAVE TO BE IN ENGLISH

@enriquesanchezb
Copy link
Author

enriquesanchezb commented Jul 15, 2019

Please, don't use comments to send the solution because this gist is public and everyone can access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment