You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many apiSharees/sharees.feature test scenarios are now passing - that is "a good thing". But there are others that are still failing, and the comment in the expected-failures file is: "These tests fail because they contain some configuration steps for oc10 specific configuration."
investigate exactly which test step is causing the failure
if possible, refactor the test scenario(s) so that they do not depend so much on oC10 specific configuration (but still keep them testing the same things!) or
raise issues (or find existing issues) to document what behavior is missing or wrong in OCIS, and add the issue references to the expected-failures file(s)
After doing this, we can decide, for each issue, if it is a feature/option that will be implemented in OCIS in the future (and leave the test running) or if the feature/option will not be supported then we can tag the scenarios "not to implement on OCIS"
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.
See cs3org/reva#1954
Many
apiSharees/sharees.feature
test scenarios are now passing - that is "a good thing". But there are others that are still failing, and the comment in the expected-failures file is: "These tests fail because they contain some configuration steps for oc10 specific configuration."After doing this, we can decide, for each issue, if it is a feature/option that will be implemented in OCIS in the future (and leave the test running) or if the feature/option will not be supported then we can tag the scenarios "not to implement on OCIS"
The text was updated successfully, but these errors were encountered: