Skip to content

Add new scenario with files #48

@Syndesi

Description

@Syndesi

In order to test file support within Ember Nexus API, it is required to add files to the reference dataset as well.

I suggest the following structure:

  • Scenario endpoint.file.getElementFile:
    • 1 user node.
    • 1 token node.
    • Data node with name missing.
      No file attached to the data node.
    • Data node with name empty.
      Empty file attached to the data node.
    • Data node with name text.
      Text file attached to the data node. Size should be around 10 KB.
    • Data node with name small.
      Small binary file attached to the data node, likely some sort of image. Size should be around 100 KB.
    • Data node with name medium.
      Medium binary file attached to the data node, likely some sort of image. Size should be around 10 MB.
    • Data node with name big.
      Big binary file attached to the data node, likely some sort of random binary file. Size should be around 90 MB.
      Note: GitHub has a limit of 100 MiB for repositories which have not enabled Git LFS.
  • Scenario endpoint.file.postElementFile:
    • 1 user node.
    • 1 token node.
    • Data nodes with the names empty, text, small, medium, big and huge with no files attached.
      The huge element should be used to test the upload of a multi GB size - ideally 6 GB.
  • Scenario endpoint.file.putElementFile:
    • 1 user node.
    • 1 token node.
    • Data node with name missing.
      No file attached to the data node.
    • Data node with name empty.
      Empty file attached to the data node.
    • Data node with name text.
      Text file attached to the data node. Size should be around 10 KB.
    • Data node with name small.
      Small binary file attached to the data node, likely some sort of image. Size should be around 100 KB.
    • Data node with name medium.
      Medium binary file attached to the data node, likely some sort of image. Size should be around 10 MB.
    • Data node with name big.
      Big binary file attached to the data node, likely some sort of random binary file. Size should be around 90 MB.
      Note: GitHub has a limit of 100 MiB for repositories which have not enabled Git LFS.
  • Scenario endpoint.file.deleteElementFile:
    • 1 user node.
    • 1 token node.
    • Data node with name missing.
      No file attached to the data node.
    • Data node with name empty.
      Empty file attached to the data node.
    • Data node with name text.
      Text file attached to the data node. Size should be around 10 KB.
    • Data node with name small.
      Small binary file attached to the data node, likely some sort of image. Size should be around 100 KB.
    • Data node with name medium.
      Medium binary file attached to the data node, likely some sort of image. Size should be around 10 MB.
    • Data node with name big.
      Big binary file attached to the data node, likely some sort of random binary file. Size should be around 90 MB.
      Note: GitHub has a limit of 100 MiB for repositories which have not enabled Git LFS.
  • Scenario endpoint.file.upload:
    • 1 user node.
    • 1 token node.
    • 1 data node.
  • Scenarios security.* receive additional File nodes, such that file-related logic can be tested.
  • Scenario security.limitedAccess.updateAccess:
    • 1 user node.
    • 1 token node.
    • 2 data nodes, both connected via HAS_READ_ACCESS and HAS_UPDATE_ACCESS

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions