It's very much feasible to run integration tests using the full CMS stack, especially if you're only looking at running tests against an API rather than testing the whole rendering stack. We have done some improvement in this area in the new CMS 11 release and I was planning on writing a blog post about this very topic. Which version are you currently running?
That sounds great! That's exacly what we're looking for since we are only interested in the communication with API's.
Looking forward to the blog post. Are you planning it in the near future? We've just upped our development-branch to CMS 11.
It's on it's way, so shouldn't be too long. Great to hear that you are on CMS 11, as it otherwise might be some differences to the process. Stay tuned and thanks for being patient!
Post is up now at https://thisisnothing.nystrom.co.nz/2017/12/05/integration-testing-with-episerver/. Hope it helps you with getting your testing going.
I'm trying to find out the best way to execute Integration-tests against the CMS. Not to be confused with Unit-tests for which we could use mocks of the relevant Episerver-related implementations. We would like to have a solution which enables us to have context which we can make operations against like we would in a real Episerver-site. This is the flow I'm imagining in the best of worlds:
I've seen examples that I've tried to replicate but I'm not fully succeeding yet. So my question is if there is anyone out there whos has pulled this (or similar) off and can give any guidance? Is this feasible or just a pipe-dream? :)