Guest User

Untitled

a guest
Jan 16th, 2018
380
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.22 KB | None | 0 0
  1. The scope of this testing is to check the event collector gets the right data/number of events on web and native.
  2. Currently, the consolidation service does not exists and require to be tested in isolation when it becomes available.
  3.  
  4.  
  5. Test scenarios covered:
  6. -----------------------
  7.  
  8. Scenario 1 - User sign up via web
  9.  
  10. Scenario 2 - User sign up via web with valid promocode
  11.  
  12. Scenario 3 - User sign up via web with invalid promocode
  13.  
  14. Scenario 4 - User sign up via mobile device (iOS & Android)
  15.  
  16. Scenario 5 - User sign up via via mobile device (iOS & Android) with valid promocode
  17.  
  18. Scenario 6 - User sign up via via mobile device (iOS & Android) with invalid promocode
  19.  
  20. Scenario 7 - Cancel sign up process and ensure event was not fired
  21.  
  22. Scenario 8 - Duplicate user sign up ensure that no event fired
  23.  
  24. Scenario 9 - Sign up with restricted state
  25.  
  26.  
  27.  
  28. Results:
  29. --------
  30.  
  31. Tested against php build 2018-01-09-b1265
  32.  
  33.  
  34. Scenario 1 - User sign up via web:
  35. ----------------------------------
  36.  
  37. signup {
  38. performing_user {
  39. user_id: 10
  40. }
  41. username: "az111"
  42. name: "az111"
  43. }
  44. }
  45. }
  46.  
  47.  
  48.  
  49. Scenario 2 - User sign up via web with valid promocode:
  50. -------------------------------------------------------
  51.  
  52. signup {
  53. performing_user {
  54. user_id: 13
  55. }
  56. username: "az333"
  57. name: "az333"
  58. promocode: "FLATRATEPROMO"
  59. }
  60. }
  61. }
  62.  
  63.  
  64.  
  65. Scenario 3 - User sign up via web with invalid promocode:
  66. ---------------------------------------------------------
  67. No event created
  68.  
  69.  
  70.  
  71. Scenario 4 - User sign up via mobile device (iOS & Android)
  72. --------------------------------------------------
  73. signup {
  74. performing_user {
  75. user_id: 11
  76. }
  77. username: "hdjrbrbr"
  78. name: "Hdjeisnen"
  79. }
  80. }
  81. }
  82.  
  83.  
  84. signup {
  85. performing_user {
  86. user_id: 12
  87. }
  88. username: "hekeoeie"
  89. name: "jekeieoe"
  90. }
  91. }
  92. }
  93.  
  94. Scenario 5 - User sign up via via mobile device (iOS & Android) with valid promocode
  95. ------------------------------------------------------------------------------------
  96. signup {
  97. performing_user {
  98. user_id: 14
  99. }
  100. username: "heiekee"
  101. name: "gsjskkww"
  102. promocode: "FLATRATEPROMO"
  103. }
  104. }
  105. }
  106.  
  107.  
  108. signup {
  109. performing_user {
  110. user_id: 15
  111. }
  112. username: "wkwnawjw8846291"
  113. name: "Salwow W"
  114. promocode: "FLATRATEPROMO"
  115. }
  116. }
  117. }
  118.  
  119.  
  120. Scenario 6 - User sign up via via mobile device (iOS & Android) with invalid promocode
  121. ------------------------------------------------------------------------------------
  122. No events fired
  123.  
  124.  
  125. Scenario 7 - Cancel sign up process and ensure event was not fired
  126. ---------------------------------------------------------
  127. No event created
  128.  
  129.  
  130.  
  131. Scenario 8 - Duplicate user sign up ensure that no event fired
  132. -------------------------------------------------------------
  133. No event created
  134.  
  135.  
  136.  
  137. Scenario 9 - Sign up with restricted state
  138. ---------------------------------------
  139.  
  140. signup {
  141. performing_user {
  142. user_id: 17
  143. }
  144. username: "geekg"
  145. name: "kjdfgkjndkln"
  146. }
  147. }
  148. }
Add Comment
Please, Sign In to add comment