Advertisement
Guest User

Untitled

a guest
Jan 18th, 2017
74
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.51 KB | None | 0 0
  1. Kamcord Manual QA Challenge
  2.  
  3. TEST PLAN
  4. For
  5. Account Creation UI.
  6.  
  7.  
  8. Purpose
  9.  
  10. This document describes the plan for testing the Account Creation UI.
  11.  
  12. Requirements for Test
  13.  
  14. The listing below identifies functional requirements and non-functional requirements that have been identified as targets for testing for the future release.
  15.  
  16.  
  17. Function Testing
  18.  
  19. Testing of the account creation page should focus on right application flow. The goals of these tests are to verify proper data acceptance, processing, and appropriate application behavior. Type of testing is - manual testing, that is verifying the application (and its internal processes) by interacting with the application via the GUI .
  20.  
  21. Test Objective:
  22.  
  23. Ensure proper application navigation, data entry and processing.
  24. Execute each case, application flow, or function, using valid and invalid data, to verify the following:
  25. The expected results occur when valid data is used.
  26. The appropriate error / warning messages are displayed when invalid data is used.
  27.  
  28.  
  29.  
  30. User Interface Testing
  31.  
  32. As well as functional testing User Interface testing is important.It verifies a user’s interaction with the software. The goal of UI Testing is to ensure that the User Interface provides the user with the appropriate access and navigation through the functions of the Create account form. In addition, UI Testing ensures that the objects within the UI function as expected.
  33.  
  34. Test Objective:
  35.  
  36. Create tests for Create account window to verify proper navigation, window objects and characteristics, such as menus, size, position, state, and focus (field to field).
  37.  
  38.  
  39.  
  40. According to page view that I have I am able to write test scenarios .
  41.  
  42. Preconditions: All fields are mandatory
  43.  
  44. Verify that entering valid data to all fields and clicking on create account should take user to success or home page.
  45.  
  46. Check the behavior of form by not filling up any data into the form and click Create Account (Verify that not filling the mandatory fields and clicking Create account button will lead to validation error) Another cases to fill the form but leave one field(User name ,Email address and Password ) blank should lead to validation error
  47.  
  48. Check the Email text field as name@gmail..com
  49.  
  50. Check the Email text field that has Email address without @ symbol. (Verify error message is displayed)
  51.  
  52. Check the upper limit of the textboxes
  53.  
  54. Verify that trying to sigh up with already existed email user gets an error message.
  55.  
  56. Verify that entering blank spaces on mandatory fields lead to validation error
  57.  
  58. Verify that password field masked with asterisks (***)
  59.  
  60. In addition, it should be tested on various devices with different screen resolution , landscape and portrait resolution. More test cases for low network, wifi/no wifi , copy/paste and more.
  61. There might be more to fully cover tested page but since it is a QA exercise I am not sure what exactly expected from me.
  62.  
  63.  
  64. Estimated time for QA team is 1-3 days to test the sigh up page
  65.  
  66.  
  67. And by looking at the image I am seeing an issue which is bug #1
  68.  
  69. Bug #1
  70.  
  71. Title: Sigh up page does not have a log in link for registered users
  72.  
  73. Steps to reproduce:
  74.  
  75. As a user who already have an account proceed to Sigh up page and Observe the UI of a page
  76.  
  77. Expected result:
  78. “Already have an account? Log in ” should be presented on the sigh up page
  79.  
  80.  
  81. Actual Result:
  82. “Already have an account? Log in ” is not presented on sigh up page
  83.  
  84.  
  85. Also there might be a logo misspeling but I dont have requirements I can not be 100% sure if its a bug or not
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement