-
Notifications
You must be signed in to change notification settings - Fork 159
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
More tests for collaborators expiration date #3132
Comments
@kiranparajuli589 @jasson99 how much of that issue is left to do? |
@individual-it @LukasHirt @jasson99 |
This is editing of user-shares and group-shares. Expiration dates are defined separately for the two share types (but in the same manner for both). We don't have user and group editing in Phoenix, yet. ;-) |
@LukasHirt what do you mean by the unit tests in |
@individual-it Yeah, unit tests are not yet in place but we want to bring them soon (#2026). For now, I'd say we can postpone that one scenario. My main reason for doing this as a unit test is that acceptance tests would need to do some gymnastics to really test it reliably since the displayed expiration date changes depending on the time of the day. So it doesn't seem worth the effort to me. Unit tests should be perfectly enough IMHO. |
Just fixed the selectors for expiration dates in the acceptance tests the other day so closing this as fixed :) we'll perhaps move some of it to unit tests soon, but let's open a new ticket for that when it gets relevant |
Follow up on #3086
Needs to be implemented:
The text was updated successfully, but these errors were encountered: