senaduka/old-new-wiaas
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Link customers to their respective (commercial leads/ resellers /shops) #34

Merged
akrdzic merged 7 commits from resseler-to-customer into master 2018-10-17 22:27:04 +02:00
Conversation 4 Commits 7 Files Changed 49 +1404 -325
akrdzic commented 2018-10-17 15:18:03 +02:00 (Migrated from gitlab.com)
Copy Link

Link customers to their respective (commercial leads/ resellers /shops)

https://app.asana.com/0/697944902557002/838943199344910

1) Preparation

execute composer install and composer update-db

2) Tests

Run unit tests and check they all passed (this PR does not contain unit tests for shop management because it would be too large but
there were some changes to existing unit test because of some changed methods)

3) Smoke test

  1. Login to backend as administrator

  2. Create Customer organization (has customer role) and customer user assigned to that organization

  3. Create 2 Commercial Lead organizations (has commercial_lead role) and user assigned to that organization

  4. Assign Customer organization as linked customer to Commercial Lead organizations

  5. Login with customer user on frontend

  6. Check that Commercial Lead shop catalogues are retrieved and available for selection

  7. Create two bundle packages ready to sell (they should have prices and countries set)

  8. Login with customer user to frontend and check that packages are not yet visible on co market for any of the shop catalogues

  9. Login with first commercial lead organization on backend

  10. Check that Product Orders and Customers menu items are present

  11. Go to Products tab and check that only bundles are visible

  12. Click to one of the bundles and set commercial lead price for it

  13. Go back to frontend customer user and check that package is now present in shop catalogue belonging to this commercial lead
    while not present in catalogue for other commercial lead

  14. Click on available package and validate prices for customer are those set by commercial lead

  15. Login to backend as other commercial lead and set prices for other bundle package

  16. Go back to frontend customer and validate that this package bundle is available for that commercial lead shop catalogue and not
    available in the catalogue of first commercial lead

  17. Click on the package and validate that customer prices are prices set by commercial lead

  18. Login as first commercial lead on backend and set prices for other package bundle

  19. Go back to frontend and check both packages are present in catalogue

  20. Open second package and validate that customer prices are prices set by first commercial lead

  21. Go to second commercial lead package shop catalogue and open the same bundle

  22. Validate that prices show are prices set by second commercial lead

  23. Login as second commercial lead to backend

  24. Set specific prices for Customer organization on already priced package bundle

  25. Go back to frontend and validate that prices shown are special customer prices

  26. Go back to backend and hide all specific commercial lead prices (deselect Visible checkboxes)

  27. Return to frontend and validate that package is not present in catalogue for customer since all prices are hidden

  28. Create another Customer organization with its own user

  29. Assign this customer to commercial leads
    30 Login as that customer to frontend

  30. Validate that both packages are visible in first commercial lead shop catalogue and one package visible in second commercial lead catalogue

  31. Validate that prices visible for package in second catalogue are default prices for that package and not
    customer specific prices set for first customer organization.

  32. Login as second commercial lead on backend

  33. Hide all default prices for already priced bundle and set at least one payment for first customer organization visible.

  34. Login as first customer

  35. Validate that package is present in catalogue and prices are customer specific prices

  36. Login as second customer

  37. validate that package is no longer visible for him.

**Link customers to their respective (commercial leads/ resellers /shops)** https://app.asana.com/0/697944902557002/838943199344910 **1) Preparation** execute `composer install` and `composer update-db` **2) Tests** Run unit tests and check they all passed (this PR does not contain unit tests for shop management because it would be too large but there were some changes to existing unit test because of some changed methods) **3) Smoke test** 1) Login to backend as administrator 2) Create Customer organization (has `customer` role) and customer user assigned to that organization 3) Create 2 Commercial Lead organizations (has `commercial_lead` role) and user assigned to that organization 4) Assign Customer organization as linked customer to Commercial Lead organizations 5) Login with customer user on frontend 6) Check that Commercial Lead shop catalogues are retrieved and available for selection 7) Create two bundle packages ready to sell (they should have prices and countries set) 8) Login with customer user to frontend and check that packages are not yet visible on co market for any of the shop catalogues 9) Login with first commercial lead organization on backend 10) Check that `Product` `Orders` and `Customers` menu items are present 11) Go to Products tab and check that only bundles are visible 12) Click to one of the bundles and set commercial lead price for it 13) Go back to frontend customer user and check that package is now present in shop catalogue belonging to this commercial lead while not present in catalogue for other commercial lead 14) Click on available package and validate prices for customer are those set by commercial lead 15) Login to backend as other commercial lead and set prices for other bundle package 16) Go back to frontend customer and validate that this package bundle is available for that commercial lead shop catalogue and not available in the catalogue of first commercial lead 17) Click on the package and validate that customer prices are prices set by commercial lead 18) Login as first commercial lead on backend and set prices for other package bundle 19) Go back to frontend and check both packages are present in catalogue 20) Open second package and validate that customer prices are prices set by first commercial lead 21) Go to second commercial lead package shop catalogue and open the same bundle 22) Validate that prices show are prices set by second commercial lead 23) Login as second commercial lead to backend 24) Set specific prices for Customer organization on already priced package bundle 25) Go back to frontend and validate that prices shown are special customer prices 26) Go back to backend and hide all specific commercial lead prices (deselect `Visible` checkboxes) 27) Return to frontend and validate that package is not present in catalogue for customer since all prices are hidden 28) Create another Customer organization with its own user 29) Assign this customer to commercial leads 30 Login as that customer to frontend 31) Validate that both packages are visible in first commercial lead shop catalogue and one package visible in second commercial lead catalogue 32) Validate that prices visible for package in second catalogue are default prices for that package and not customer specific prices set for first customer organization. 33) Login as second commercial lead on backend 34) Hide all default prices for already priced bundle and set at least one payment for first customer organization visible. 35) Login as first customer 36) Validate that package is present in catalogue and prices are customer specific prices 37) Login as second customer 38) validate that package is no longer visible for him.
akrdzic commented 2018-10-17 17:45:44 +02:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

Compare with previous version

added 1 commit <ul><li>0238f914 - Fixes</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/34/diffs?diff_id=25332699&start_sha=4d13ee40bce09da8aec0a62b5f89b3de4488e236)
akrdzic commented 2018-10-17 19:40:34 +02:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

Compare with previous version

added 1 commit <ul><li>49281f02 - remove error logs</li></ul> [Compare with previous version](https://gitlab.com/saburly/wiaas/new-wiaas/merge_requests/34/diffs?diff_id=25347541&start_sha=0238f9140e4f7690c5d2221d12d084b3e086a634)
bilal.catic commented 2018-10-17 22:27:04 +02:00 (Migrated from gitlab.com)
Copy Link

merged

merged
bilal.catic commented 2018-10-17 22:27:04 +02:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit c8ed5f7ff8

mentioned in commit c8ed5f7ff81f6766a032a0ca701556e0c5b97038
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
senaduka
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: senaduka/old-new-wiaas#34
Delete Branch "resseler-to-customer"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?