Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Always activate testing using pytest fixture. | Elrond | 2013-05-17 | 1 | -1/+27 |
| | | | | | | | | | | | | | This is possibly the cleaner approach to the problem solved in the previous commit. The previous commit makes sure, that testing is enabled at import time. While this one enables it just before the individual test is run. So this one takes a bit more CPU. Maybe revert the previous commit? References: 0536306048daa0970d2e43411ba2a9bf073e570e | ||||
* | Switch test_app generation over to use py.test fixtures. | Christopher Allan Webber | 2013-04-04 | 1 | -0/+15 |
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 |