I'm currently leaning on the Node + Angular stack and utilising Karma and Protractor for testing.
I'm currently having a hard time figuring out how to handle E2E tests that create and edit data, as well the need to have a expected data loaded.
Searching google turns up lots of various custom methods. I often read 'you should set-up your data' or 'just create a mock' without going into a bit more detail on a common process. Others put in too much overhead in creating a whole new mock module from scratch.
I would just to know how are people currently doing it, and is there a standard for this? Or do people tend to just mock the back-end? Mocking the back-end doesn't seem to be simple either like in Karma since your in the browser scope.
I am as expected using MongoDB, so would be nice to get some direction on what other doing in this scenario. Particularly automating loading of fixtures and database clean-up through Protractor would be good.
Protractor is for e2e testing only. that means, it hast nothing to do with your database. you could use a task runner (like grunt or gulp) to clean-up and fill your database and after that let the task runner start your protractor tests (i never did the last, but i think it is possible). well, i know it's not the answer you were aiming to, but maybe i could point you to the right direction.