Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change Testcases function according to kiboengage and kibochat #100

Open
arveenkumar55 opened this issue Nov 22, 2018 · 13 comments
Open

Change Testcases function according to kiboengage and kibochat #100

arveenkumar55 opened this issue Nov 22, 2018 · 13 comments
Assignees

Comments

@arveenkumar55
Copy link
Contributor

you need to change the test cases according to kiboengage and kibochat.

@arveenkumar55
Copy link
Contributor Author

Today I changed test cases according to Kiboengage and tomorrow I will change test cases according to skibochat.

@sojharo
Copy link
Contributor

sojharo commented Dec 5, 2018

Arveen, please update here regarding our conversation of how we would test after we merge restructure work on production. We had discussed and please let know what steps were taken.

@sojharo sojharo added the High label Dec 5, 2018
@sojharo
Copy link
Contributor

sojharo commented Dec 6, 2018

If this is working for restructure of staging then let's work on how it would work for restructure of production as well.

@jekram
Copy link

jekram commented Dec 6, 2018

This is critical and high priority

@arveenkumar55
Copy link
Contributor Author

I am working.

@arveenkumar55
Copy link
Contributor Author

@jekram today i have done changes now we can run on Production. Tomorrow I will run these testcases on production.

@jekram
Copy link

jekram commented Dec 7, 2018

Why did we not run the automated test here? Why did we defer it to tomorrow?

@arveenkumar55
Copy link
Contributor Author

Tested these modules on Production.

  1. Polls
  2. Survey
  3. Broadcast
  4. comment capture
  5. Dashboard
  6. Invite member
  7. Manage Pages
  8. Subscriber
  9. segment subscriber
  10. Wizard
  11. Subscriber

Result:
Majority of testcases of these modules run successfully but few of these testcases require data.
For example: For Pagination testing we need list of data so few of the test has failed.

Found issue
I have found some issue issue on Production but these issue is already solved in staging. Should i need to open separate issue on GitHub? For example: there is a issue in header , Action button in smart replies is not working etc.

@arveenkumar55
Copy link
Contributor Author

Initially i have tested these modules on app.kibopush.com(Production). Now we have divided our product into two separate product so i will change testcases according to kibochat and kiboengage.

@arveenkumar55
Copy link
Contributor Author

arveenkumar55 commented Dec 14, 2018

I have changed testcases according to kiboengage and kibochat on production and run following modules.

  1. Login
  2. Signup
  3. forgot password
  4. Polls
  5. survey
  6. Broadcast
  7. Dashboard
    found issue(recaptcha is not working properly in production accounts#183, sent and isresponded are always zero in Polls,survey and Broadcast  KiboEngage#173, file and image is not uploading KiboEngage#174)
    Remaining will run on Monday.

@arveenkumar55
Copy link
Contributor Author

arveenkumar55 commented Dec 17, 2018

Tested these modules on Production.
1. sequence messaging
2. comment capture
3. Manage Pages
4. Subscriber
5. segment subscriber
6. Wizard
7. Subscriber
8. Setting
9. Invite using phone number
10. menu

Found issue:
Cloudkibo/KiboEngage#153, Cloudkibo/KiboEngage#175, Cloudkibo/KiboChat#116

@arveenkumar55
Copy link
Contributor Author

arveenkumar55 commented Dec 19, 2018

Tested remaining modules on Production.

  1. Persistent menu
  2. setting
  3. smart replies
  4. Members
    Found issue(should immediately update or display message after send pdf file in livechat KiboEngage#198, delete button is not working in subscriber tags KiboEngage#195)

@arveenkumar55
Copy link
Contributor Author

This is complete. we can resolve this issue.

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

No branches or pull requests

3 participants