Skip to content
This repository has been archived by the owner on Feb 22, 2023. It is now read-only.

split loadtest.py into "CRUD"-like modules #16

Closed
rpappalax opened this issue Mar 11, 2017 · 3 comments
Closed

split loadtest.py into "CRUD"-like modules #16

rpappalax opened this issue Mar 11, 2017 · 3 comments

Comments

@rpappalax
Copy link
Collaborator

loadtest_read.py (for read, search, list)

  • global_setup: login, create 100 users

loadtest_create.py (for create)

  • global_setup: login

loadtest_delete.py (delete_logins)

  • setup: login, create 100 users
@pdehaan
Copy link
Collaborator

pdehaan commented Mar 11, 2017

img_0467

@pdehaan
Copy link
Collaborator

pdehaan commented Mar 13, 2017

This is blocked because we cannot upload any images in a @global_setup or @setup due to the fact that you need to be logged in to perform a create_shot() action. Currently both the @global_setup and @setup methods are used to create the session object that are used by the scenarios.

Not sure how we can write/maintain a synchronous (for setup) and asynchronous (for scenarios) versions of these methods.
We could write a synchronous version of create_shot() for our read_shot scenario, but then we'll also need to rewrite all the login/register functionality as well.

We could just point the read_shot scenario to an existing image on stage (since a user doesn't need to be logged in to view a shot, but that doesn't help us with the list_shots and search_shots scenarios, where a user will need to have X existing shots and be logged in to run the tests.

@pdehaan
Copy link
Collaborator

pdehaan commented Mar 28, 2017

I think we're CRUDdy enough to close this.

@pdehaan pdehaan closed this as completed Mar 28, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants