{"action":"created","issue":{"url":"https://api.github.com/repos/ArtooTrills/Bounty-QA-Zomato/issues/2","labels_url":"https://api.github.com/repos/ArtooTrills/Bounty-QA-Zomato/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/ArtooTrills/Bounty-QA-Zomato/issues/2/comments","events_url":"https://api.github.com/repos/ArtooTrills/Bounty-QA-Zomato/issues/2/events","html_url":"https://github.com/ArtooTrills/Bounty-QA-Zomato/pull/2","id":101242079,"number":2,"title":"Rename README.md to QA Reply.md","user":{"login":"anoopsfr97","id":13816918,"avatar_url":"https://avatars.githubusercontent.com/u/13816918?v=3","gravatar_id":"","url":"https://api.github.com/users/anoopsfr97","html_url":"https://github.com/anoopsfr97","followers_url":"https://api.github.com/users/anoopsfr97/followers","following_url":"https://api.github.com/users/anoopsfr97/following{/other_user}","gists_url":"https://api.github.com/users/anoopsfr97/gists{/gist_id}","starred_url":"https://api.github.com/users/anoopsfr97/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/anoopsfr97/subscriptions","organizations_url":"https://api.github.com/users/anoopsfr97/orgs","repos_url":"https://api.github.com/users/anoopsfr97/repos","events_url":"https://api.github.com/users/anoopsfr97/events{/privacy}","received_events_url":"https://api.github.com/users/anoopsfr97/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-08-16T08:14:32Z","updated_at":"2015-08-19T06:20:11Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/ArtooTrills/Bounty-QA-Zomato/pulls/2","html_url":"https://github.com/ArtooTrills/Bounty-QA-Zomato/pull/2","diff_url":"https://github.com/ArtooTrills/Bounty-QA-Zomato/pull/2.diff","patch_url":"https://github.com/ArtooTrills/Bounty-QA-Zomato/pull/2.patch"},"body":"Hi,\r\n I will be writing the test cases below for Zomato Web App, Zomato Mobile app and Zomato API\r\n\r\nTest Cases for Zomato Web App:\r\n1.Verifying that Zomato app is opening in various browsers.(eg-Chrome,Firefox,IE)\r\n2.Verifying that Zomato app works in various OS.eg-Windows,Mac,etc\r\n3.Verifying that ZOmato app is not causing a problem for other app present in the system/machine already.\r\nThe above 3 test cases will form the base for Pre-conditions testing.\r\n\r\n4.Verifying that functionality of the entire Zomato web app.\r\n-This will include testing like clicks on all buttons/options\r\n-Testing the GUI part like the placement of images and button and how they look on the web page.\r\n-Checking for Inputs like whether user is able to type in the text box-eg Searching for a restaurant and user is able to type in the test box.\r\n-Checking for the output is as per the input given-eg-Restaurant details for restaurant searched.\r\n-Checking that proper value is returned from database as per the search done or query made.\r\n Based on Test Plan above few Test cases are as below:\r\na.Verify that user is able to select a city\r\nb.Verify that user is able to type restaurant name in \"Search for restaurant field\".\r\nc.Verify that user can give special characters or numbers or alphabets in \"Search for Restaurant field\"\r\nd.Verify that result returned after search is relevant.\r\ne.Verify on giving improper restaurant name, user gets proper information message stating the reason.\r\nf.Verify that on selecting a city, restaurants of that city are only shown and not of other cities.eg City is Bangalore and restaurants are of Chennai. \r\ng.Verify that on clicking on \"Search for restaurant\", user gets option to select from a  list of options or  enter the restaurant name.\r\nh.Verify that all information displayed for a  search is up-to-date eg-Location,menu,Timings,Pricing,etc\r\n\r\n5. We also check for Non-functional part of the App which includes:\r\na.Security of the app - eg-If any payment is to be done\r\nb.Recovery for the app - If the app crashes while doing payment or due to any other reason.\r\nc.App Performance - Number of people visiting the app at same time so the load and stress testing comes in picture\r\nd.Configuration,Compatibility testing - This includes different softwares/OS/Browsers/Hardware related.\r\ne.Usability testing like how it looks,flow,reporting format,usage.\r\n\r\nOnce all these are done with positive testing and negative testing,we can move ahead with the release of the app.\r\n\r\n6.Then it will include Smoke testing before the release\r\n\r\nThe same will go with Mobile App and with Zomato API.\r\nZomato API testing will be bit different as it only needs to be integrated and tested that it will have no effect on existing system. \r\nAlso we can automated things for the APP as we move ahead.\r\n\r\n\r\nExample for a Test Plan and the cases included for Mobile Zomato App:\r\nZOmato Mobile App\"\r\n\r\nTest plan for Download of app:\r\n1.Verify user is able to download the app from Play Store.\r\n2.Verify that all the permissions for data collection are shown to user before download begins.\r\n3.Verify that user is able to open app on successful download.\r\n4.Verify that if download halts in middle due to connectivity issue, it resumes are the issue is solved.\r\n\r\nTest Plan for Functionality of app:\r\n1.Verify user is able to scroll through the app smoothly.\r\n2.Verify that user is able to select city, and tap on other options provided\r\n3.Verify that user is able to tap on search and he gets a list of restaurant type to select or type restaurant name.\r\n4.Verify that on selecting a particular type, those restaurant list are shown.\r\n5.Verify that user can sort as per the option provided.\r\n6.Verify that on selecting a restaurant, user is shown details about that restaurant only\r\n7.Verify the GUI part of that page.\r\n8.Verify for options on that page.\r\n\r\n\r\nThere are many  more cases and scenarios that can be taken up like app performance and wifi issue and many more. I will stop here for now.\r\n\r\nFor low literate users, the basic thing is language.\r\nIf user is know to the language, he is definitely going to use the app.\r\nThe UI and UX can be kept as simple as possible at the start of the page. The basic functionality of zomato is searching a restaurant so \"Search\" should be a most visible part on UI side.\r\n\r\nFor connectivity, taking India as an example,\r\nHere majority people have Smartphone but the Internet usage in these smartphone is mostly 2G which is a slow. So keeping this in mind, the app should be designed in such a way that it takes least time to load the app and dividing the app city wise,makes it more better for searching restaurant  in app as it will filter out other restaurants giving a list of only that city."},"comment":{"url":"https://api.github.com/repos/ArtooTrills/Bounty-QA-Zomato/issues/comments/132459802","html_url":"https://github.com/ArtooTrills/Bounty-QA-Zomato/pull/2#issuecomment-132459802","issue_url":"https://api.github.com/repos/ArtooTrills/Bounty-QA-Zomato/issues/2","id":132459802,"user":{"login":"kaushikbhat","id":5136009,"avatar_url":"https://avatars.githubusercontent.com/u/5136009?v=3","gravatar_id":"","url":"https://api.github.com/users/kaushikbhat","html_url":"https://github.com/kaushikbhat","followers_url":"https://api.github.com/users/kaushikbhat/followers","following_url":"https://api.github.com/users/kaushikbhat/following{/other_user}","gists_url":"https://api.github.com/users/kaushikbhat/gists{/gist_id}","starred_url":"https://api.github.com/users/kaushikbhat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kaushikbhat/subscriptions","organizations_url":"https://api.github.com/users/kaushikbhat/orgs","repos_url":"https://api.github.com/users/kaushikbhat/repos","events_url":"https://api.github.com/users/kaushikbhat/events{/privacy}","received_events_url":"https://api.github.com/users/kaushikbhat/received_events","type":"User","site_admin":false},"created_at":"2015-08-19T06:20:11Z","updated_at":"2015-08-19T06:20:11Z","body":"Hi Anoop,\n\nThis is a good initial start. We like the detailed test cases you have\nprovided. Can you automate running few of these test cases using any tools\nlike Android MonkeyRunner, Selenium or any other tool of your choice.\nBasically we want to see, how comfortable are you with scripting and\nautomation and delving into a little bit of coding as well if required. Try\nto implement something either for the Mobile or the Web (Doing both would\nbe a bonus)\n\nBest, Kaushik\n\n--\nKaushik Bhat, Engineer, *Artoo | *+91-888-458-6227\n\nOn Sun, Aug 16, 2015 at 1:44 PM, anoopsfr97 <notifications@github.com>\nwrote:\n\n> Hi,\n> I will be writing the test cases below for Zomato Web App, Zomato Mobile\n> app and Zomato API\n>\n> Test Cases for Zomato Web App:\n> 1.Verifying that Zomato app is opening in various\n> browsers.(eg-Chrome,Firefox,IE)\n> 2.Verifying that Zomato app works in various OS.eg-Windows,Mac,etc\n> 3.Verifying that ZOmato app is not causing a problem for other app present\n> in the system/machine already.\n> The above 3 test cases will form the base for Pre-conditions testing.\n>\n> 4.Verifying that functionality of the entire Zomato web app.\n> -This will include testing like clicks on all buttons/options\n> -Testing the GUI part like the placement of images and button and how they\n> look on the web page.\n> -Checking for Inputs like whether user is able to type in the text box-eg\n> Searching for a restaurant and user is able to type in the test box.\n> -Checking for the output is as per the input given-eg-Restaurant details\n> for restaurant searched.\n> -Checking that proper value is returned from database as per the search\n> done or query made.\n> Based on Test Plan above few Test cases are as below:\n> a.Verify that user is able to select a city\n> b.Verify that user is able to type restaurant name in \"Search for\n> restaurant field\".\n> c.Verify that user can give special characters or numbers or alphabets in\n> \"Search for Restaurant field\"\n> d.Verify that result returned after search is relevant.\n> e.Verify on giving improper restaurant name, user gets proper information\n> message stating the reason.\n> f.Verify that on selecting a city, restaurants of that city are only shown\n> and not of other cities.eg City is Bangalore and restaurants are of\n> Chennai.\n> g.Verify that on clicking on \"Search for restaurant\", user gets option to\n> select from a list of options or enter the restaurant name.\n> h.Verify that all information displayed for a search is up-to-date\n> eg-Location,menu,Timings,Pricing,etc\n>\n>    1. We also check for Non-functional part of the App which includes:\n>    a.Security of the app - eg-If any payment is to be done b.Recovery for the\n>    app - If the app crashes while doing payment or due to any other reason.\n>    c.App Performance - Number of people visiting the app at same time so the\n>    load and stress testing comes in picture d.Configuration,Compatibility\n>    testing - This includes different softwares/OS/Browsers/Hardware related.\n>    e.Usability testing like how it looks,flow,reporting format,usage.\n>\n> Once all these are done with positive testing and negative testing,we can\n> move ahead with the release of the app.\n>\n> 6.Then it will include Smoke testing before the release\n>\n> The same will go with Mobile App and with Zomato API.\n> Zomato API testing will be bit different as it only needs to be integrated\n> and tested that it will have no effect on existing system.\n> Also we can automated things for the APP as we move ahead.\n>\n> Example for a Test Plan and the cases included for Mobile Zomato App:\n> ZOmato Mobile App\"\n>\n> Test plan for Download of app:\n> 1.Verify user is able to download the app from Play Store.\n> 2.Verify that all the permissions for data collection are shown to user\n> before download begins.\n> 3.Verify that user is able to open app on successful download.\n> 4.Verify that if download halts in middle due to connectivity issue, it\n> resumes are the issue is solved.\n>\n> Test Plan for Functionality of app:\n> 1.Verify user is able to scroll through the app smoothly.\n> 2.Verify that user is able to select city, and tap on other options\n> provided\n> 3.Verify that user is able to tap on search and he gets a list of\n> restaurant type to select or type restaurant name.\n> 4.Verify that on selecting a particular type, those restaurant list are\n> shown.\n> 5.Verify that user can sort as per the option provided.\n> 6.Verify that on selecting a restaurant, user is shown details about that\n> restaurant only\n> 7.Verify the GUI part of that page.\n> 8.Verify for options on that page.\n>\n> There are many more cases and scenarios that can be taken up like app\n> performance and wifi issue and many more. I will stop here for now.\n>\n> For low literate users, the basic thing is language.\n> If user is know to the language, he is definitely going to use the app.\n> The UI and UX can be kept as simple as possible at the start of the page.\n> The basic functionality of zomato is searching a restaurant so \"Search\"\n> should be a most visible part on UI side.\n>\n> For connectivity, taking India as an example,\n> Here majority people have Smartphone but the Internet usage in these\n> smartphone is mostly 2G which is a slow. So keeping this in mind, the app\n> should be designed in such a way that it takes least time to load the app\n> and dividing the app city wise,makes it more better for searching\n> restaurant in app as it will filter out other restaurants giving a list of\n> only that city.\n> ------------------------------\n> You can view, comment on, or merge this pull request online at:\n>\n>   https://github.com/ArtooTrills/Bounty-QA-Zomato/pull/2\n> Commit Summary\n>\n>    - Rename README.md to QA Reply.md\n>\n> File Changes\n>\n>    - *R* QA Reply.md\n>    <https://github.com/ArtooTrills/Bounty-QA-Zomato/pull/2/files#diff-0>\n>    (0)\n>\n> Patch Links:\n>\n>    - https://github.com/ArtooTrills/Bounty-QA-Zomato/pull/2.patch\n>    - https://github.com/ArtooTrills/Bounty-QA-Zomato/pull/2.diff\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/ArtooTrills/Bounty-QA-Zomato/pull/2>.\n>\n"}}