-
Notifications
You must be signed in to change notification settings - Fork 0
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
Regression test fails - Kim needs access to other calendars for better coverage #1476
Comments
@kmdvs Can you please remind me which all addresses needs to added to other calendars? |
@sahalali the 4 accounts are |
@sahalali I still can't change to any other calendar, in Staging or in Production |
@sahalali can you please add Kim's 4 emails (above) to all calendars so that regression tests work whenever you test (either from staging or production) |
@sahalali To update the script that copies data from production to staging, Kim's account needs to be added to all calendars in staging. Additionally, a script should be developed to copy data locally. |
The script that add developer accounts are now modified to add Kim's 4 accounts to staging when ever data is copied from production to staging. From now on Kim's emails have access to all the calendars in staging. |
Added @kmdvs's comment from #1453
The RT aren't designed for other calendars than Tout Culture... At least, not yet, since I never tested another calendar... It would be great to give my 4 accounts access to all calendars, so I can actually make appropriate changes based on what calendar IS tested. In theory, since the code-base for all calendars is pretty similar (correct me if I am wrong), and the RT use the UI, and the UI don't change that much between calendars, nothing suggests a specific calendar should pose a particular problem other than small exceptions (like clicking on an additional button to edit something, or using an additional drop-down before saving an event).
I would need specific information on what fails to investigate, and more importantly, access to all calendars for my 4 accounts in production :)
The text was updated successfully, but these errors were encountered: