Bradley Temple's Profile

Integration Tests are always going to be relatively slow, as you have to wait on the actual request/response cycles and page rendering, which is a lot more overhead. While there is some stuff you can do to dull the pain, practically you may want to stick to running javascripty tests on Travis or another CI if you aren't making active changes to the feature in question. (IE, run your focused tests, and let the CI build tell you if you broke something unintentionally)