thelonecabbage/django-superbulk

Django app/view that adds the ability to execute many requests inside of a single HTTP connection

django-superbulk's Issues

Add superbulk_transactional view for handling the Django requests in a big transaction

https://github.com/thelonecabbage/django-superbulk/blob/master/views.py#L10

Need

As a developer
I want to be able to send multiple requests to the Django API within a database transaction
So that all requests succeed or fail atomically within a transaction

• I'm not sure what the output should be when the transaction fails
• our use-case is that of django-tastypie in combination with superbulk to simulate some kind of REST transactions
• TransactionMiddleware from Django is an option, but it is not granular at all (either for all views or for none)

Deliverables

• superbulk_transactional view where all operations is wrapped in a transaction (it should actually call the normal superbulk view)
• each Django view call should be within a try-catch block, because some of them might fail (what is the expected response in this case?)
• automated test for all of these situations

Add superbulk_transactional view for handling the Django requests in a big transaction

https://github.com/thelonecabbage/django-superbulk/blob/master/views.py#L10

Need

As a developer
I want to be able to send multiple requests to the Django API within a database transaction
So that all requests succeed or fail atomically within a transaction

• I'm not sure what the output should be when the transaction fails
• our use-case is that of django-tastypie in combination with superbulk to simulate some kind of REST transactions
• TransactionMiddleware from Django is an option, but it is not granular at all (either for all views or for none)

Deliverables

• superbulk_transactional view where all operations is wrapped in a transaction (it should actually call the normal superbulk view)
• each Django view call should be within a try-catch block, because some of them might fail (what is the expected response in this case?)
• automated test for all of these situations

Add regression test for bug #4

Need:

In order to not regress to old bugs
As a developer
I need tests to confirm recent/future changes do not open old bugs

Solution:

• Add unit(without gherkin feature) in the django-superbulk/django_superbulk/atomic_superbulk/tests.py that calls endpoint with scenario described in #4
• Find solution(maybe make a script) to run in one command both gherkin and unit tests
• Update readme with new way of running tests

Refactoring:

• Rename atomic_superbulk app into test_app (we don't need to create separate django apps for each feature we test)

Django test app improvements

Need:

Test running should be clean and accurate.

Deliverables:

Running tests with the command from the README.md doesn't work because of:

• if you have a version of django_superbulk installed it uses that, so you're not testing what you actually changed in the repo(if you don't re-install after each change)

Solution:

• in the urls.py of the test app we should import the views from the repo:

+# Assure that the superbulk functions are used from the current repo, not
+# the installed package
+import imp
+django_superbulk = imp.load_source('django_superbulk', '../django_superbulk.py')


 urlpatterns = patterns('',

-    url(r'^api/superbulk/', 'django_superbulk.superbulk', name='superbulk-api'),
-    url(r'^api/superbulk_transactional/', 'django_superbulk.superbulk_transactional',
+    url(r'^api/superbulk/', django_superbulk.superbulk, name='superbulk-api'),
+    url(r'^api/superbulk_transactional/', django_superbulk.superbulk_transactional,

Add it to PIP

Need

For more reach, we should add the project to the PIP mirror so users can easily install a specific version or update.

make proper environment initialisation for tests

In order to run tests sandboxed 
As a developer
I need to have the database created each time tests are run

Solution

Add the database creation before tests are started, and delete database after tests are run.