aboutsummaryrefslogtreecommitdiffstats
path: root/mediagoblin/tests/test_csrf_middleware.py
Commit message (Collapse)AuthorAgeFilesLines
* trac#665: Upgrade to WebTest 2.0.18 and fix broken test `test_csrf_cookie_set`.Ben Sturmfels2015-11-051-2/+2
| | | | | | | | Test was failing due to API change in WebTest around accessing cookies set in the test client. These are now in `test_app.cookies`. While there are currently 48 other tests failing, I've verified that before and after this change that the same number fail. I've also checked that no other tests use the old API for accessing test client cookies. I've pinned to version 2.0.18. My understanding is that it's generally a good idea to pin to a specific version where possible to avoid the "why has this suddenly broken" type bugs. This also seems appropriate since WebTest appears to be very stable.
* Reverting "Always activate testing in every test module ever."Christopher Allan Webber2013-05-171-3/+0
| | | | | | Revert "Always activate testing in every test module ever." This reverts commit 0536306048daa0970d2e43411ba2a9bf073e570e.
* Always activate testing in every test module ever.Christopher Allan Webber2013-05-161-0/+3
| | | | Kind of a dorky way to implement this, but...
* Switch test_app generation over to use py.test fixtures.Christopher Allan Webber2013-04-041-10/+10
| | | | | | | | | | | | By doing this, we can take advantage of py.test's ability to create temporary directories that are then cleaned up later during testing. This helps for sandboxing things. This also involves a ton of changes: - Changing the get_app stuff appropriately, getting rid of the setup_fresh_app decorator - Making said fixture - Switching over a billion tests to use it
* Rename get_test_app to get_app.Elrond2013-01-181-4/+4
| | | | | | | nosetests runs everything that even vaguely looks like a test case... even our get_test_app. And as it is imported everywhere... it is run everywhere as a test case. Renaming it saves us about 10+ tests and a few seconds of time.
* Fix tests on webtest < 1.3.6.Elrond2013-01-091-1/+5
| | | | | | | | | | | Debian testing ships webtest 1.3.4. And it would be nice to use the base packages. One of the csrf tests fails on webtest < 1.3.6. But using a fresh app fixes it. We have no clue, why exactly. When we require webtest 1.3.6, change this.
* tests: More instances where a fresh database is not neededSebastian Spaeth2013-01-081-10/+7
| | | | Save test runtime by not dumping the databases when not needed.
* Fix CSRF tests with webtest 1.4.0Sebastian Spaeth2012-12-111-3/+3
| | | | | | | | | | CSRF tests apparently passed with earlier versions of webtest, but failed with the latest webtest (1.4.0) package. It choked on passing a "key=value; " cookie as it split at the semicolon and failed to find additional values or something like that. Removing the semicolon makes this test pass. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
* Fix problems from pyflakes outputWill Kahn-Greene2012-06-031-5/+0
|
* It's 2012 all up in hereChristopher Allan Webber2012-02-021-1/+1
|
* Issue 680 Allow decorating views to prevent CSRF protection.Nathan Yergler2011-11-261-1/+20
|
* Hotfix: Renaming cookie broke unit testsElrond2011-10-161-1/+3
| | | | | | | | The name of the cookie was hardcoded in the unit tests and while renaming the cookie this part was missed. So now read the cookie_name from the config in the test. This also tests for the config item existing!
* #361 Unit tests for CSRF MiddlewareNathan Yergler2011-10-011-0/+69