github.com/cs3org/reva/v2@v2.27.7/tests/acceptance/features/apiVirtualViews/virtualViews.feature (about)

     1  @api @virtual-views-required
     2  Feature: virtual views
     3    As admin
     4    I want to be able to shard large folders over multiple storage providers
     5    So that I can scale large numbers of users better.
     6  
     7    Background:
     8      Given user "einstein" deletes everything from folder "virtual/" using the WebDAV API
     9      And user "einstein" has created the following folders
    10        | path            |
    11        | virtual/a       |
    12        | virtual/a/alice |
    13        | virtual/b       |
    14        | virtual/c       |
    15        | virtual/k       |
    16        | virtual/l       |
    17        | virtual/z       |
    18  
    19    Scenario: list large folder
    20      Given using old DAV path
    21      When user "einstein" lists the resources in "/virtual" with depth "0" using the WebDAV API
    22      Then the HTTP status code should be "207"
    23      And the last DAV response for user "einstein" should not contain these nodes
    24        | name      |
    25        | virtual/a |
    26        | virtual/b |
    27        | virtual/c |
    28        | virtual/k |
    29        | virtual/l |
    30        | virtual/z |
    31      When user "einstein" lists the resources in "/virtual" with depth 1 using the WebDAV API
    32      Then the HTTP status code should be "207"
    33      And the last DAV response for user "einstein" should contain these nodes
    34        | name |
    35        | virtual/a    |
    36        | virtual/b    |
    37        | virtual/c    |
    38        | virtual/k    |
    39        | virtual/l    |
    40        | virtual/z    |
    41      And the last DAV response for user "einstein" should not contain these nodes
    42        | name            |
    43        | virtual/a/alice |
    44      When user "einstein" lists the resources in "/virtual" with depth "infinity" using the WebDAV API
    45      Then the HTTP status code should be "207"
    46      And the last DAV response for user "einstein" should contain these nodes
    47        | name            |
    48        | virtual/a       |
    49        | virtual/a/alice |
    50        | virtual/b       |
    51        | virtual/c       |
    52        | virtual/k       |
    53        | virtual/l       |
    54        | virtual/z       |
    55  
    56    Scenario: etag changes when adding a folder
    57      Given user "einstein" has stored etag of element "/"
    58      And user "einstein" has stored etag of element "/virtual"
    59      And user "einstein" has stored etag of element "/virtual/b"
    60      When user "einstein" creates folder "/virtual/b/bar" using the WebDAV API
    61      Then these etags should have changed:
    62        | user     | path       |
    63        | einstein | /          |
    64        | einstein | /virtual   |
    65        | einstein | /virtual/b |