Skip to content
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

Add new scenario with files #48

Open
Syndesi opened this issue May 5, 2024 · 0 comments
Open

Add new scenario with files #48

Syndesi opened this issue May 5, 2024 · 0 comments
Milestone

Comments

@Syndesi
Copy link
Member

Syndesi commented May 5, 2024

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.
@Syndesi Syndesi added this to the 0.1.0 milestone May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant